List public posts that quote a specified Bluesky post by its at:// URI. Use optional cursor and limit for pagination.
List quotes of a Bluesky post. Returns public posts that quote the specified post, with an optional cursor for pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | The quoted post's at:// URI | |
| limit | No | Page size, 1-100 | |
| cursor | No | Pagination cursor |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It adds meaningful context by stating that only public posts are returned and that a cursor supports pagination. It does not mention auth needs, default limits, ordering, or response shape, but for a simple read/list endpoint this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler, and the core action is front-loaded in the first words. Each clause adds useful information about scope or pagination.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a three-parameter list tool with full schema coverage and no output schema, the description covers the key decision points: what a quote is, that results are public, and that pagination is possible. It could mention the default page size or describe the returned post fields, but these are minor gaps given the endpoint's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents all three parameters with 100% coverage. The description only restates the cursor's pagination purpose and refers to the URI as 'the specified post', adding little semantic value beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource ('List quotes of a Bluesky post') and adds that it returns public posts, so an agent can tell what the tool does. However, it does not explicitly differentiate this from sibling Bluesky tools like bluesky_post_likes and bluesky_post_reposted_by; the distinction is only implied by the word 'quotes'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case is reasonably clear from the description: retrieve posts that quote a given Bluesky post, with pagination support. However, there is no explicit guidance about when to choose this tool over related Bluesky interaction tools, so the agent must infer the choice from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.