WebCull CLI Is A Programmable Bookmark Interface
The WebCull CLI lets you, your scripts, and your agent tools inspect and update bookmarks from a terminal. It works best when you start with small results, choose only the fields you need, and make focused follow-up requests.
webcull <command> [options]
Install And Run The CLI
Install from npm, authorize WebCull, then run a small command. Agent skills are optional for guided agent workflows.
npm install -g @webcull/cli.
webcull login, then compare the pairing code to authorize with your account.
webcull whoami or webcull graph schema.
webcull@webcull/clihttps://api.webcull.com~/.config/webcull/config.jsonUse The CLI When Bookmarks Become Data
Start Broad, Then Narrow By ID
webcull whoami
webcull bookmarks count --path /
webcull bookmarks tree --path / --max-depth 1 --limit 25 --fields id,type,title
webcull bookmarks search --query 'pricing competitor' --limit 20 --fields id,title,url,parent_id
webcull bookmarks get --ids 2302 --fields id,title,url,notes
The normal pattern is to find likely IDs with a small command, then fetch details only for those IDs. This keeps responses fast and easier to review.
Run These Commands First
These commands establish account access, show current limits, and inspect the account without requesting a large result. They are the safest starting point for humans, scripts, and agents.
webcull login
webcull whoami
webcull limits
webcull bookmarks count --path /
webcull bookmarks tree --path / --max-depth 1 --limit 25 --max-chars 8000 --fields id,type,title,modified
Choose The Smallest Command That Answers The Question
login, whoami, limitsbookmarks count, tree, getbookmarks searchgraph around, backlinks, pathbookmarks create, updatereminders create, list, cancelThe CLI Is Conservative By Default
Read commands support limits. Write commands are narrow. E2EE passphrases stay in hidden terminal prompts. Tokens live in operating system credential storage. Graph commands are read-only and exclude notes unless you request extra fields.