Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm

List who an account follows

get_follows
Read-onlyIdempotent

Get the accounts a given Bluesky user follows by providing their handle or DID. Automatically pages through all results to return the complete list.

Instructions

Accounts a given account follows. Pages automatically.

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.
Install Server

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds the useful 'Pages automatically' behavior, which goes beyond what the annotations state.

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?

The description is very short and front-loads the core purpose, then adds the key pagination behavior. Every word earns its place.

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 simple read-only listing tool with a documented required parameter and safety annotations, the description is nearly complete. It could mention the return shape, but the tool name and title make the expected output clear.

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?

The schema describes actor, limit, and account, leaving only cursor without a description. The description contributes no parameter-level meaning, but schema coverage is strong enough that the gap is minor.

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?

The title and description clearly indicate the tool lists the accounts a given account follows. It is easily distinguished from the sibling get_followers, which lists followers instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is the tool to call for seeing an account's follow list, but it does not explicitly state when to prefer it over get_followers or other list tools. The 'Pages automatically' note is behavior, not usage guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thenavidm/bluesky-mcp-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server