Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List followers

get_followers
Read-onlyIdempotent

Retrieve accounts that follow a specified Bluesky account, newest first, with automatic pagination beyond 100 results.

Instructions

Accounts that follow a given account, newest first. Pages automatically past Bluesky's 100 ceiling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorYesHandle or DID.
limitNoHow many. Default 50.
cursorNo
accountNoWhich connected account to act as, by handle (for example 'alice.bsky.social' or just 'alice'). Defaults to the first connected account. Call list_accounts to see them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, open-world, non-destructive. The description adds key behavioral detail: results are sorted newest first, and pagination automatically handles Bluesky's 100-item ceiling. This goes beyond annotations.

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?

Two concise sentences that front-load the resource and include a key pagination note. No wasted words.

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?

For a read-only list tool with no output schema, the description covers ordering and pagination behavior, which are crucial. It omits mention of cursor usage, but the schema covers that. Nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, so most parameters are documented. The description doesn't add format or constraints beyond what the schema provides (e.g., actor as handle/DID, limit default). Baseline 3 is appropriate when schema does heavy lifting.

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 (list) and resource (followers of a given account) with clear scope. Distinguishes from siblings like get_follows (the inverse) and search_actors by specifying 'Accounts that follow a given account'.

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?

Implies use for retrieving followers, but does not explicitly state when to use this versus alternatives like get_follows (the inverse). Still clear enough for an agent to infer from the description and name.

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