Skip to main content
Glama

bluesky-mcp-server

Get Bluesky List or Starter Pack

bsky_get_list
Read-onlyIdempotent

Read a Bluesky list or starter pack with list, or discover one actor’s public lists or starter packs with actor and kind. Direct reads return metadata and one membership page. To read posts, pass a list URI or a starter pack feedUri to bsky_get_feed.

Input Schema

NameRequiredDescriptionDefault
kindNoCollection to discover for actor. Required with actor. Omit with list.
listNoList or starter pack AT-URI or bsky.app page. Use for a direct membership read.
actorNoHandle, @handle, DID, or bsky.app profile URL. Use with kind to discover collections.
limitNoMaximum members or discovery results to return. Default 25. Values above 100 are clamped unless read-limit clamping is disabled.
cursorNoNonempty opaque cursor from a previous page of the same list or the same actor and kind.

Output Schema

NameRequiredDescriptionDefault
capNoLimit applied to this page.
listNoRequested list metadata, or the starter pack’s backing list metadata.
errorNoPresent when the call failed. Absent on success.
listsNoLists visible on this discovery page.
shownNoNumber of members or discovery results on this page.
cursorNoOpaque cursor as supplied by Bluesky. Reuse a nonempty value with the same list or actor and kind, even after an empty page. An empty or absent cursor ends pagination.
noticeNoLimit clamp or reason starter pack membership is unavailable.
membersNoMembership records on this page. Absent if membership is unavailable or this is a discovery page.
truncatedNoTrue when Bluesky supplied a nonempty continuation cursor.
starterPackNoRequested starter pack metadata.
starterPacksNoStarter packs visible on this discovery page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so safety is covered. The description adds real value beyond them by disclosing the result shape — metadata plus only one membership page — which tells the agent that pagination/`cursor` will be needed for full membership. It does not mention auth requirements or rate limits, keeping it short of 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.

Conciseness5/5

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

Three sentences, no filler, with the two read modes front-loaded and the hand-off to bsky_get_feed placed last where it belongs. Every clause carries operational 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?

An output schema exists, so return values need not be explained, and the description still flags the single-page result limit. What is missing is secondary: authentication/privacy context for reading a list and whether discovery includes only public collections is only implied by 'public'.

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 description coverage is 100%, so the baseline is 3. The description earns an extra point by restating the tricky `anyOf` mutual-exclusion in plain prose (list alone, or actor with kind), which is the one thing hard to extract from the raw JSON schema.

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 (read / discover) against specific resources (list, starter pack, an actor's public lists or starter packs) and explicitly separates the two operating modes by parameter. An agent can distinguish it from siblings like bsky_get_feed 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?

Gives explicit routing: use `list` for a direct read, use `actor` + `kind` for discovery, and use bsky_get_feed when the goal is reading posts. That is both when-to-use and a named alternative with the condition that selects it.

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.