Skip to main content
Glama

Taproot: AT Protocol MCP

list_repos_by_collection

Read-only

Network-wide: which accounts publish a given collection/lexicon,e.g. 'who has an app.bsky.feed.generator (a custom feed)?' or who uses a custom lexicon. Via a relay's com.atproto.sync.listReposByCollection (anonymous). By default returns DIDs only (one request, large page); pass enrich=true to also resolve handles (slower, smaller page). For just a total, use count_repos_by_collection. NOTE: relay-served (defaults to the public Bluesky relay; pass relay to query another), not the account's own PDS. Pairs with search_lexicons / resolve_lexicon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (1-1000, default 1000). With enrich=true the effective page is capped near 20 (each DID is resolved to a handle). Use the returned cursor for the next page.
relayNoOptional relay origin to query instead of the default, e.g. https://relay.example.com.
cursorNoPagination cursor from a previous call.
enrichNoResolve each DID to its handle. Default false — returns DIDs only in ONE request (large page, the fast path for listing/counting). Set true only when you need handles (slower, smaller page).
collectionYesA collection NSID, e.g. app.bsky.feed.generator.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint/openWorldHint, and the description goes further: it discloses the anonymous relay-served path, that the default is the public Bluesky relay rather than the account's PDS, and the speed/size tradeoff between DIDs-only and enrich=true. It stops short of discussing error behavior or rate limits, so not a 5.

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-loads the core purpose and example before caveats, and every clause carries operational meaning. It is dense and slightly run-on with stacked parentheticals, but nothing is wasted.

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 an output schema present, return values need no explanation, and the description covers scope, transport (relay vs PDS), pagination intent, and enrichment tradeoffs. Nothing essential for correct invocation is missing.

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%, so 3 is the baseline, but the description adds value beyond the schema by clarifying that the relay defaults to the public Bluesky relay (the schema only says 'default') and by re-framing the enrich/limit interaction. Clear marginal contribution.

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+resource (list repos publishing a given collection) with concrete examples ('who has an app.bsky.feed.generator?'), and explicitly differentiates from count_repos_by_collection, search_lexicons, and resolve_lexicon. An agent can identify the right tool without opening any schema.

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 it (enumerate publishers of a collection) and when not to (use count_repos_by_collection for just a total). Names the relay default and how to query another, plus the pairing tools, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources