Skip to main content
Glama
cameronrye

AT Protocol MCP Server

remove_bookmark

DestructiveIdempotent

Remove a private bookmark from a post by providing its AT-URI. Deleting a non-existent bookmark has no effect.

Instructions

Remove a private bookmark from a post on AT Protocol (app.bsky.bookmark.deleteBookmark). Takes the bookmarked post AT-URI — bookmarks are keyed by post URI, there is no separate bookmark-record URI. Removing a bookmark that does not exist succeeds as a no-op. Requires authentication (app password). Use add_bookmark to add and get_bookmarks to list. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesAT-URI of the bookmarked post (at://did/app.bsky.feed.post/rkey). Bookmarks are keyed by the post URI — pass the post URI itself, not a bookmark-record URI (none exists).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the remove operation succeeded.
messageYesHuman-readable status message.
wasBookmarkedYesTrue when the post was confirmed bookmarked before removal. False when it was not bookmarked, or when the prior state could not be confirmed — in that case the delete is still issued and the server treats deleting a missing bookmark as a no-op.
removedBookmarkYesThe post whose bookmark was removed (or confirmed absent).
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes idempotent behavior ('removing a bookmark that does not exist succeeds as a no-op'), authentication requirements ('requires authentication (app password)'), and rate limiting. Adds value beyond annotations like destructiveHint and idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with purpose, no redundant information. Efficiently covers usage, behavior, and auth.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists (inferred), description fully explains behavior (no-op), auth needs, and rate limiting. Complete for a simple removal tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Provides context on the 'uri' parameter beyond schema: clarifies that bookmarks are keyed by post URI, not a bookmark-record URI, and instructs to pass the post URI directly. With 100% schema coverage, this is useful additional guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (remove a private bookmark) and resource (post bookmark on AT Protocol). Distinguishes from siblings by mentioning add_bookmark and get_bookmarks, providing contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool (to remove a bookmark), what happens if bookmark doesn't exist (no-op), and references alternatives (add_bookmark, get_bookmarks).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cameronrye/atproto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server