AT Protocol MCP Server

get_bookmarks

Read-only

List your private bookmarks with cursor pagination. Each entry shows the full post view or an unavailable reason.

Instructions

List the authenticated account's private bookmarks (app.bsky.bookmark.getBookmarks) with cursor pagination. Each entry carries the full bookmarked post view when the post is still viewable, or an unavailableReason (blocked / not_found) when it is not. Requires authentication (app password). Use add_bookmark / remove_bookmark to manage bookmarks. Subject to per-tool rate limiting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bookmarks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max bookmarks per page (1–100, default 50).
`cursor`	No	Opaque pagination cursor from the previous response cursor field; omit for the first page.

Output Schema

Name	Required	Description
`success`	Yes	Whether the request succeeded.
`bookmarks`	Yes	The bookmarks for this page.
`cursor`	No	Opaque cursor for the next page; absent when there are no more results.
`hasMore`	Yes	Whether additional pages of results are available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jun 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
Addedv0.6.0Jun 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds value beyond annotations: explains read-only operation, authentication requirements, rate limiting, cursor pagination, and unavailable reasons. No contradiction with annotations (readOnlyHint, openWorldHint).

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?

Three sentences, no wasted words. First sentence states purpose, second details return behavior, third covers authentication and sibling tools. Well-structured and efficient.

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?

With output schema present, return values need no explanation. Description covers pagination, authentication, rate limiting, and error states (unavailable reasons). Fully complete for a read-only listing tool.

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

Parameters3/5

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

Schema coverage is 100% with parameter descriptions already in the schema. The description mentions cursor pagination but adds no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states 'List the authenticated account's private bookmarks' with a specific verb and resource. It also distinguishes from sibling tools add_bookmark and remove_bookmark.

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

Usage Guidelines4/5

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

Provides context for when to use (list bookmarks) and mentions management via siblings. While it doesn't explicitly state when not to use, the pagination, authentication, and rate-limit discussion offer sufficient guidance.

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