WebCull
cli

Output And Limits

Control response size, field selection, paging, and output format.

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.

Use The Same Controls Across Read Commands

--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.

Start With Small Payloads

webcull bookmarks tree --path / --max-depth 1 --limit 25 --max-chars 8000 --fields id,type,title,modified
webcull graph around --stack-id 2301 --depth 1 --limit 50 --max-chars 12000
webcull bookmarks get --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.

Next step cli E2EE And Safety Use CLI commands safely with encrypted accounts and hidden passphrase prompts.