Skip to main content
Glama

get_follows

Retrieve a list of users followed by a Bluesky account, supporting pagination for browsing through follows.

Instructions

Get users followed by an account.

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

Returns:
    List of followed accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNo
limitNo
cursorNo

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the get_follows tool logic. It retrieves the list of accounts followed by a user (or the authenticated user if no handle provided), handles pagination with limit and cursor, and returns the data wrapped in a success/error dict.
    @mcp.tool()
    def get_follows(
        ctx: Context,
        handle: Optional[str] = None,
        limit: Union[int, str] = 50,
        cursor: Optional[str] = None,
    ) -> Dict:
        """Get users followed by an account.
    
        Args:
            ctx: MCP context
            handle: Optional handle to get follows for. If None, gets the authenticated user
            limit: Maximum number of results to return (1-100)
            cursor: Optional pagination cursor
    
        Returns:
            List of followed accounts
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            # If no handle provided, get authenticated user's follows
            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_follows directly with positional arguments as per the client signature
            follows_response = bluesky_client.get_follows(handle, cursor, limit)
            follows_data = follows_response.dict()
    
            return {"status": "success", "follows": follows_data}
        except Exception as e:
            error_msg = f"Failed to get follows: {str(e)}"
            return {"status": "error", "message": error_msg}
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 it returns a 'List of followed accounts' and includes pagination via 'cursor', but it doesn't specify authentication requirements, rate limits, error conditions, or what happens if the handle doesn't exist. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured and front-loaded with the purpose, followed by clear sections for Args and Returns. Every sentence adds value without redundancy, making it efficient and easy to parse. The bullet-point-like format enhances readability without unnecessary verbosity.

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 the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameters but lacks details on authentication, error handling, and output structure (e.g., what fields are in the returned list). Without annotations or an output schema, more context would be helpful for reliable use.

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

Parameters4/5

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

The description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'handle' is optional and defaults to the authenticated user, 'limit' has a range (1-100), and 'cursor' is for pagination. This compensates well for the schema's lack of descriptions, though it doesn't detail the format of 'handle' or 'cursor' values.

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 followed by an account.' It specifies the verb ('Get') and resource ('users followed by an account'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_followers' (which gets followers rather than follows), though the distinction is implied by the name.

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 provides some usage context by noting that if 'handle' is None, it gets follows for the authenticated user, which implies when to use this parameter. However, it doesn't offer explicit guidance on when to choose this tool over alternatives like 'get_followers' or 'get_profile', nor does it mention any prerequisites or exclusions.

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