Skip to main content
Glama
brianellin

Bluesky MCP Server

by brianellin

search-people

Find and retrieve users or actors on Bluesky using a search query, with customizable result limits up to 100 entries.

Instructions

Search for users/actors on Bluesky

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to fetch (1-100)
queryYesSearch query for finding users

Implementation Reference

  • Full implementation of the 'search-people' tool: registers the tool with schema (query string, optional limit) and handler that uses AtpAgent to search Bluesky actors/users, formats results with display name, handle, DID, bio, stats.
      "search-people",
      "Search for users/actors on Bluesky",
      {
        query: z.string().describe("Search query for finding users"),
        limit: z.number().min(1).max(100).default(20).describe("Number of results to fetch (1-100)"),
      },
      async ({ query, limit }) => {
        if (!agent) {
          return mcpErrorResponse("Not logged in. Please check your environment variables.");
        }
    
        try {
          const response = await agent.app.bsky.actor.searchActors({ q: query, limit });
          
          if (!response.success) {
            return mcpErrorResponse("Failed to search for users.");
          }
    
          const { actors } = response.data;
          
          if (actors.length === 0) {
            return mcpSuccessResponse(`No users found for query: "${query}"`);
          }
    
          const results = actors.map((actor: any, index: number) => {
            return `User #${index + 1}:
    Display Name: ${actor.displayName || 'No display name'}
    Handle: @${actor.handle}
    DID: ${actor.did}
    ${actor.description ? `Bio: ${actor.description}` : 'Bio: No bio provided'}
    ${actor.followersCount !== undefined ? `Followers: ${actor.followersCount}` : ''}
    ${actor.followsCount !== undefined ? `Following: ${actor.followsCount}` : ''}
    ${actor.postsCount !== undefined ? `Posts: ${actor.postsCount}` : ''}
    ${actor.indexedAt ? `Indexed At: ${new Date(actor.indexedAt).toLocaleString()}` : ''}
    ---`;
          }).join("\n\n");
    
          return mcpSuccessResponse(results);
        } catch (error) {
          return mcpErrorResponse(`Error searching for users: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Search' implies a read-only operation, it doesn't describe important behavioral aspects like rate limits, authentication requirements, pagination behavior, or what the return format looks like (especially since there's no output schema). This leaves significant gaps for an agent to understand how to use it 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 extremely concise - a single sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded with the core functionality and wastes no space on redundant information.

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?

For a search tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the search returns (user profiles? handles? DIDs?), how results are ranked, whether there are authentication requirements, or any limitations. Given the complexity of search functionality and the lack of structured metadata, more context is needed.

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?

The description mentions 'Search for users/actors' which implies the 'query' parameter is for user/actor searches, but doesn't add meaningful semantic context beyond what the schema already provides. With 100% schema description coverage (both parameters have clear descriptions in the schema), the baseline is 3 - the description doesn't compensate but doesn't need to since the 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 tool's purpose with a specific verb ('Search') and resource ('users/actors on Bluesky'), making it immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'search-feeds' or 'search-posts', which would require mentioning the specific domain of user/actor searches versus content searches.

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 when this search is appropriate compared to other user-related tools like 'get-profile' or 'get-followers', nor does it specify any prerequisites or exclusions for usage.

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