Skip to main content
Glama
berlinbra

BlueSky MCP Server

bluesky_search_profiles

Search for user profiles on the BlueSky social network using queries to find specific accounts or discover new ones.

Instructions

Search for Bluesky profiles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
limitNoMaximum number of results to return (default 25, max 100)
cursorNoPagination cursor for next page of results

Implementation Reference

  • Registration of the 'bluesky_search_profiles' tool within the list_tools function, including name, description, and input schema definition.
    types.Tool(
        name="bluesky_search_profiles",
        description="Search for Bluesky profiles",
        inputSchema={
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "Search query string",
                },
                "limit": {
                    "type": "integer",
                    "description": "Maximum number of results to return (default 25, max 100)",
                    "default": 25,
                },
                "cursor": {
                    "type": "string",
                    "description": "Pagination cursor for next page of results",
                },
            },
            "required": ["query"],
        },
    ),
  • Input schema for the 'bluesky_search_profiles' tool, defining required 'query' parameter and optional 'limit' and 'cursor'.
    inputSchema={
        "type": "object",
        "properties": {
            "query": {
                "type": "string",
                "description": "Search query string",
            },
            "limit": {
                "type": "integer",
                "description": "Maximum number of results to return (default 25, max 100)",
                "default": 25,
            },
            "cursor": {
                "type": "string",
                "description": "Pagination cursor for next page of results",
            },
        },
        "required": ["query"],
    },
  • Handler implementation for 'bluesky_search_profiles' tool within the call_tool function. Validates query, extracts parameters, calls the Bluesky search_actors API, and returns JSON response.
    elif name == "bluesky_search_profiles":
        query = arguments.get("query")
        if not query:
            return [types.TextContent(type="text", text="Missing required argument: query")]
        limit = arguments.get("limit", 25)
        cursor = arguments.get("cursor")
        response = await asyncio.to_thread(
            bluesky.client.app.bsky.actor.search_actors,
            {'term': query, 'limit': limit, 'cursor': cursor}
        )
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. 'Search for Bluesky profiles' implies a read-only operation, but it doesn't disclose key traits like rate limits, authentication needs, pagination behavior (beyond the cursor parameter in schema), error handling, or what the results include (e.g., profile details). 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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a search tool. Every word earns its place, making it easy to parse quickly.

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, no output schema, and 3 parameters, the description is incomplete. It lacks information on behavioral traits (e.g., rate limits), result format, and usage context. For a search tool with potential complexity in results and pagination, more detail is needed to help an agent invoke it correctly without relying solely on the schema.

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 clear descriptions for query, limit, and cursor parameters. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain query syntax, result ordering, or cursor usage). Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't compensate with extra context.

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 'Search for Bluesky profiles' clearly states the action (search) and resource (Bluesky profiles). It distinguishes from sibling tools like bluesky_search_posts (which searches posts) and bluesky_get_profile (which retrieves a specific profile). However, it doesn't specify the scope or type of search (e.g., by username, display name, keywords), making it slightly less specific than ideal.

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 to prefer bluesky_search_profiles over bluesky_get_profile (for specific profiles) or bluesky_search_posts (for content search), nor does it indicate any prerequisites or exclusions. Usage is implied by the name 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/berlinbra/BlueSky-MCP'

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