Identify Bluesky users who reposted a specific post. Use the post's at:// URI to retrieve public repost actors with pagination support for large result sets.
List actors who reposted a Bluesky post. Returns public actors who reposted a post, with an optional cursor for pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | The 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?
With no annotations, the description carries the burden of behavioral disclosure. It usefully states that the returned actors are public and that pagination is supported via cursor, but it does not mention authentication needs, rate limits, or response structure. It adds some transparency without being comprehensive.
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 brief and front-loaded with the primary purpose. The second sentence repeats 'reposted a post' and adds only the pagination detail, making it slightly redundant but not bloated.
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?
This is a simple one-required-parameter tool with well-documented parameters, but there is no output schema and no description of the returned actor fields or pagination shape. The description is adequate for basic invocation but leaves material gaps for an agent handling the response.
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 at 100% coverage, so the baseline applies. The description's mention of an optional pagination cursor adds no meaning beyond what the schema's 'Pagination cursor' description already 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 clearly states the action and resource: listing actors who reposted a Bluesky post. It is specific enough to distinguish the tool from siblings like bluesky_post_likes and bluesky_post_quotes by the core action, though it never names or references those alternatives explicitly.
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 description provides no guidance on when to choose this tool over alternatives, no exclusions, and no prerequisites. The use case is only implied by the tool name and basic purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.