Skip to main content
Glama
brianellin

Bluesky MCP Server

by brianellin

follow-user

Enables AI assistants to follow a specific user on Bluesky by providing the user's handle. Part of the Bluesky MCP Server for managing social interactions on the ATProtocol.

Instructions

Follow a user on Bluesky

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesThe handle of the user to follow

Implementation Reference

  • The handler function that implements the 'follow-user' tool. It resolves the provided handle to a DID using agent.resolveHandle, then calls agent.follow(did) to perform the follow action, with proper error handling.
      if (!agent) {
        return mcpErrorResponse("Not logged in. Please check your environment variables.");
      }
    
      try {
        // Resolve the handle to a DID
        const resolveResponse = await agent.resolveHandle({ handle: cleanHandle(handle) });
        
        if (!resolveResponse.success) {
          return mcpErrorResponse(`Failed to resolve handle: ${handle}`);
        }
        
        const did = resolveResponse.data.did;
        await agent.follow(did);
        
        return mcpSuccessResponse(`Successfully followed @${handle}`);
      } catch (error) {
        return mcpErrorResponse(`Error following user: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input schema using Zod: requires a 'handle' parameter which is a string describing the user's handle (e.g., alice.bsky.social).
      handle: z.string().describe("The handle of the user to follow"),
    },
    async ({ handle }) => {
  • src/index.ts:681-707 (registration)
    The MCP server.tool registration for the 'follow-user' tool, including name, description, input schema, and handler reference.
      "follow-user",
      "Follow a user on Bluesky",
      {
        handle: z.string().describe("The handle of the user to follow"),
      },
      async ({ handle }) => {
        if (!agent) {
          return mcpErrorResponse("Not logged in. Please check your environment variables.");
        }
    
        try {
          // Resolve the handle to a DID
          const resolveResponse = await agent.resolveHandle({ handle: cleanHandle(handle) });
          
          if (!resolveResponse.success) {
            return mcpErrorResponse(`Failed to resolve handle: ${handle}`);
          }
          
          const did = resolveResponse.data.did;
          await agent.follow(did);
          
          return mcpSuccessResponse(`Successfully followed @${handle}`);
        } catch (error) {
          return mcpErrorResponse(`Error following user: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Follow a user' which implies a write/mutation operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, idempotency (e.g., what happens if already following), or response format. For a mutation tool with zero 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place.

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 this is a mutation tool with no annotations, no output schema, and 1 parameter, the description is incomplete. It lacks critical context such as authentication needs, error conditions, what the tool returns, or how it differs from read-only sibling tools. The description should do more to compensate for missing structured data.

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 the single parameter 'handle' documented as 'The handle of the user to follow'. The description adds no additional meaning beyond what the schema provides (e.g., format examples like '@user.bsky.social' or validation rules). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Follow') and target ('a user on Bluesky'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'get-followers' or 'get-follows', which are read operations rather than write operations. The purpose is unambiguous but lacks sibling distinction.

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 prerequisites (e.g., authentication status), exclusions, or compare with related tools like 'get-follows' (for checking follows) or 'search-people' (for finding users). Usage context is implied but not explicit.

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

Related 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/brianellin/bsky-mcp-server'

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