Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

bluesky_post_reposted_by

List Bluesky accounts that reposted a specific post using its at:// URI. Supports pagination via limit and cursor to retrieve reposters in pages.

Instructions

List actors who reposted a Bluesky post. Lists the accounts that reposted a Bluesky post, identified by its at:// post uri, which is required. limit defaults to 25 and is capped at 100; pass the returned cursor back for the next page. Each actor has did, handle, display_name, description, avatar_url and created_at.

Input Schema

NameRequiredDescriptionDefault
uriYesThe post's at:// URI
limitNoPage size, 1-100
cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it usefully discloses the pagination contract (cursor round-trip), the default page size (25), the hard cap (100), and the exact actor fields returned. It doesn't discuss rate limits or auth requirements, but the core behavioral mechanics are covered.

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

Conciseness4/5

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

Front-loaded with purpose, then parameters, then return shape — an efficient ordering. However, the first two sentences are near-duplicates ('List actors who reposted...' / 'Lists the accounts that reposted...'), which wastes a sentence that could carry new information.

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

Completeness4/5

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

With no output schema and no annotations, the description compensates by enumerating the returned actor fields and explaining pagination, and all three parameters are accounted for. It is complete enough to invoke correctly, though it omits any auth/rate-limit context for a public API.

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?

Schema coverage is 100%, giving a baseline of 3, but the description adds real value beyond the schema: the `limit` default of 25 (the schema only states the 1-100 range) and the instruction to feed the returned `cursor` back for the next page. It also restates that `uri` is required and expects an at:// form.

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?

States a specific verb and resource ('List actors who reposted a Bluesky post') and pins the scope to a single post via its at:// URI. An agent can distinguish it from siblings like bluesky_post_likes or bluesky_post_quotes from the description alone.

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?

Gives clear usage context: the `uri` is required, `limit` defaults to 25 and is capped at 100, and the returned `cursor` should be passed back for paging. It does not explicitly name an alternative tool (e.g., likes/quotes siblings) or state when-not to use it, so it stops short of the highest tier.

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

Deploy Server

Other Tools