Skip to main content
Glama
enesjakozh
berlinbra

BlueSky MCP Server

by berlinbra
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

bluesky_get_followers

Retrieve a list of accounts following a user on BlueSky, with pagination support to manage large follower counts.

Instructions

Get a list of accounts following the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of followers to return (default 50, max 100)
cursorNoPagination cursor for next page of results

Implementation Reference

  • src/bluesky_mcp/server.py:230-236 (handler)
    Handler implementation for bluesky_get_followers tool: calls the Bluesky API to get followers of the authenticated user with optional limit and cursor.
    elif name == "bluesky_get_followers":
    limit = arguments.get("limit", 50)
    cursor = arguments.get("cursor")
    response = await asyncio.to_thread(
        bluesky.client.app.bsky.graph.get_followers,
        {'actor': IDENTIFIER, 'limit': limit, 'cursor': cursor}
    )
  • src/bluesky_mcp/server.py:106-123 (registration)
    Registration of the bluesky_get_followers tool in the list_tools handler, including description and input schema.
    types.Tool(
    name="bluesky_get_followers",
    description="Get a list of accounts following the user",
    inputSchema={
        "type": "object",
        "properties": {
            "limit": {
                "type": "integer",
                "description": "Maximum number of followers to return (default 50, max 100)",
                "default": 50,
            },
            "cursor": {
                "type": "string",
                "description": "Pagination cursor for next page of results",
            },
        },
    },
),
  • src/bluesky_mcp/server.py:109-122 (schema)
    Input schema definition for the bluesky_get_followers tool.
    inputSchema={
    "type": "object",
    "properties": {
        "limit": {
            "type": "integer",
            "description": "Maximum number of followers to return (default 50, max 100)",
            "default": 50,
        },
        "cursor": {
            "type": "string",
            "description": "Pagination cursor for next page of results",
        },
    },
},

Tool Definition Quality

C2.9/5.0
Behavior2/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 of behavioral disclosure. While 'Get a list' implies a read-only operation, it doesn't specify critical details like authentication requirements, rate limits, pagination behavior beyond the cursor parameter, or the format of the returned list (e.g., usernames, IDs, profiles). This leaves significant gaps for an agent to use the tool effectively.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the complexity of a social media API tool with no annotations and no output schema, the description is insufficient. It fails to address key contextual elements like authentication needs, error handling, or the structure of returned data (e.g., list of profiles vs. usernames), which are crucial for an agent to invoke the tool correctly in real-world scenarios.

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 description coverage is 100%, with clear documentation for both parameters (limit and cursor), including defaults and purposes. The description adds no additional parameter information beyond what the schema provides, which is acceptable given the high coverage, resulting in a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get a list') and resource ('accounts following the user'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'bluesky_get_follows' (which likely retrieves accounts the user follows), but the phrase 'following the user' provides enough context to distinguish it from other tools in the Bluesky context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'bluesky_get_profile' (which might include follower counts) or 'bluesky_search_profiles' (which could find followers via search). It also lacks information about prerequisites, such as whether authentication is required or if it works for any user.

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

Install Server

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/berlinbra/BlueSky-MCP'

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