Skip to main content
Glama
berlinbra

BlueSky MCP Server

bluesky_get_follows

Retrieve a list of accounts you follow on BlueSky with pagination support to manage large following lists efficiently.

Instructions

Get a list of accounts the user follows

Input Schema

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

Implementation Reference

  • Handler logic for executing the bluesky_get_follows tool. Calls the Bluesky graph.get_follows API to fetch the list of followed accounts for the authenticated user, using provided limit and cursor parameters.
    elif name == "bluesky_get_follows":
        limit = arguments.get("limit", 50)
        cursor = arguments.get("cursor")
        response = await asyncio.to_thread(
            bluesky.client.app.bsky.graph.get_follows,
            {'actor': IDENTIFIER, 'limit': limit, 'cursor': cursor}
        )
  • Tool registration in the list_tools() function, defining the name, description, and input schema for bluesky_get_follows.
    types.Tool(
        name="bluesky_get_follows",
        description="Get a list of accounts the user follows",
        inputSchema={
            "type": "object",
            "properties": {
                "limit": {
                    "type": "integer",
                    "description": "Maximum number of follows to return (default 50, max 100)",
                    "default": 50,
                },
                "cursor": {
                    "type": "string",
                    "description": "Pagination cursor for next page of results",
                },
            },
        },
    ),
  • Input schema definition for the bluesky_get_follows tool, specifying optional limit and cursor parameters.
    inputSchema={
        "type": "object",
        "properties": {
            "limit": {
                "type": "integer",
                "description": "Maximum number of follows to return (default 50, max 100)",
                "default": 50,
            },
            "cursor": {
                "type": "string",
                "description": "Pagination cursor for next page of results",
            },
        },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior beyond the cursor parameter, or what the output format looks like (e.g., list structure, included fields). This is inadequate for a tool with potential complexity.

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, clear sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a straightforward tool, making it easy to parse and understand immediately.

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 no annotations and no output schema, the description is incomplete. It doesn't explain the return format (e.g., what data fields are included for each account), error conditions, authentication requirements, or how pagination works in practice. For a social media API tool that likely returns structured data, this leaves significant gaps for an AI agent.

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 both parameters ('limit' and 'cursor') well-documented in the schema itself. The description adds no additional parameter semantics beyond implying a list is returned, which is already clear from the tool name and schema. This meets the baseline for high schema coverage.

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 verb ('Get') and resource ('list of accounts the user follows'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'bluesky_get_followers' beyond the obvious directional difference, missing an opportunity to clarify the specific relationship being queried.

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_followers' (for followers instead of follows) or 'bluesky_get_profile' (which might include follow data). There's no mention of prerequisites, context, or comparison to sibling tools, leaving usage decisions entirely to inference.

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