Skip to main content
Glama

get_followers

Retrieve follower lists for Bluesky accounts to analyze audience connections and manage social relationships.

Instructions

Get users who follow an account.

Args:
    ctx: MCP context
    handle: Optional handle to get followers for. If None, gets the authenticated user
    limit: Maximum number of results to return (1-100)
    cursor: Optional pagination cursor

Returns:
    List of follower accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNo
limitNo
cursorNo

Implementation Reference

  • The primary handler function for the 'get_followers' tool, registered via @mcp.tool(). It retrieves the list of followers for a given Bluesky handle (or the authenticated user's handle if none provided), with support for pagination via limit and cursor parameters. Uses the atproto Client's get_followers method and wraps the response in a standard success/error dictionary format.
    @mcp.tool()
    def get_followers(
        ctx: Context,
        handle: Optional[str] = None,
        limit: Union[int, str] = 50,
        cursor: Optional[str] = None,
    ) -> Dict:
        """Get users who follow an account.
    
        Args:
            ctx: MCP context
            handle: Optional handle to get followers for. If None, gets the authenticated user
            limit: Maximum number of results to return (1-100)
            cursor: Optional pagination cursor
    
        Returns:
            List of follower accounts
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            # If no handle provided, get authenticated user's followers
            if not handle:
                handle = bluesky_client.me.handle
    
            # Convert limit to int if it's a string
            if isinstance(limit, str):
                limit = int(limit)
            limit = max(1, min(100, limit))
    
            # Call get_followers directly with positional arguments as per the client signature
            followers_response = bluesky_client.get_followers(handle, cursor, limit)
            followers_data = followers_response.dict()
    
            return {"status": "success", "followers": followers_data}
        except Exception as e:
            error_msg = f"Failed to get followers: {str(e)}"
            return {"status": "error", "message": error_msg}
  • server.py:1075-1076 (registration)
    The 'get_followers' tool is listed under the 'profiles' category in the tools information resource provided at 'info://bluesky-tools'. This serves as a form of tool discovery or registration metadata.
    "profiles": ["get_profile", "get_follows", "get_followers", "follow_user"],
    "posts": [
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. It mentions that if 'handle' is None, it gets the authenticated user's followers, which adds some context. However, it lacks critical details: it doesn't specify authentication needs (implied but not stated), rate limits, pagination behavior beyond the cursor parameter, or what the returned list structure looks like. For a tool with no annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose, followed by clear sections for Args and Returns. Each sentence adds value without redundancy. It could be slightly more concise by integrating the default behavior into the main description, but overall it's efficient and easy to parse.

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

Completeness3/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 does a fair job: it covers the tool's purpose and parameters adequately. However, it lacks details on authentication requirements, error handling, and the structure of returned data (beyond 'List of follower accounts'), which are important for a social media API tool. It's minimally viable but has clear gaps in context.

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 0%, so the description must compensate. It adds meaningful semantics for all three parameters: 'handle' (optional, defaults to authenticated user), 'limit' (range 1-100), and 'cursor' (pagination). This goes beyond the schema's basic titles. However, it doesn't explain parameter interactions or provide examples, leaving some ambiguity (e.g., how 'handle' interacts with authentication).

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 tool's purpose: 'Get users who follow an account.' It specifies the verb ('Get') and resource ('users who follow an account'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_follows' (which might get accounts that a user follows rather than followers of an account), leaving room for potential confusion.

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. It doesn't mention sibling tools like 'get_follows' or 'get_profile' that might retrieve related data, nor does it specify prerequisites such as authentication requirements or context for when fetching followers is appropriate. Usage is implied but not explicitly stated.

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/gwbischof/bluesky-social-mcp'

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