WebCull - Documentation - Output And Limits

Output

Keep CLI Responses Bounded And Readable

Use clear limits on list-style commands. This keeps terminal output readable on large accounts and gives agent tools small enough results to review carefully.

Usage Limits

Check Current CLI Usage

Run webcull limits to see the selected account's current read and write usage before running many commands.

webcull limits --account <account-hash>

Controls

Use The Same Controls Across Read Commands

--account <hash|id>

Selects which locally authorized WebCull account supplies the token for this command. Agents should use the account hash.

--limit <n>

Maximum number of rows or nodes returned.

--page <n>

Page number for commands that support paging.

--fields <list>

Comma-separated fields such as id,title,url,parent_id,modified.

--max-chars <n>

Maximum response size.

--max-metadata-chars <n>

Maximum text length for large bookmark detail fields.

--format json|jsonl

Pretty JSON is the default. JSONL prints one item per line when a response contains an item list.

Examples

Start With Small Payloads

webcull bookmarks tree --account <account-hash> --path / --max-depth 1 --limit 25 --max-chars 8000 --fields id,type,title,modified
webcull graph around --account <account-hash> --stack-id 2301 --depth 1 --limit 50 --max-chars 12000
webcull bookmarks get --account <account-hash> --ids 2302 --fields id,title,url,notes --max-metadata-chars 1200

When a response is too broad, reduce fields first, then reduce long text fields, then reduce row limits. Increase one limit at a time.

Retry Guidance

Respect Structured Retry Responses

The CLI preserves retryable response codes so people, scripts, and agents can respond without guessing. request_busy means another request for the same account is still running. request_lock_unavailable means request coordination could not be checked. Wait for the supplied retry time before trying again.

{
  "success": "false",
  "code": "request_busy",
  "retry_after_ms": 1000
}

A throttled response includes retry_after_seconds. Wait at least that long, then reduce limits, output size, or query breadth before continuing. The CLI does not automatically retry writes.