Skip to main content
Glama
berlinbra

BlueSky MCP Server

bluesky_search_posts

Search for posts on the Bluesky social network using keywords to find relevant content and discussions.

Instructions

Search for posts on Bluesky

Input Schema

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

Implementation Reference

  • Handler logic for the 'bluesky_search_posts' tool. Extracts query (required), limit (default 25), cursor, and invokes the Bluesky app.bsky.feed.search_posts API via asyncio.to_thread.
    elif name == "bluesky_search_posts":
        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.feed.search_posts,
            {'q': query, 'limit': limit, 'cursor': cursor}
        )
  • Tool registration in @server.list_tools(), defining name, description, and inputSchema with required 'query', optional 'limit' (default 25), and 'cursor'.
    types.Tool(
        name="bluesky_search_posts",
        description="Search for posts on Bluesky",
        inputSchema={
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "The search query",
                },
                "limit": {
                    "type": "integer",
                    "description": "Maximum number of posts to return (default 25, max 100)",
                    "default": 25,
                },
                "cursor": {
                    "type": "string",
                    "description": "Pagination cursor for next page of results",
                },
            },
            "required": ["query"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function. It doesn't disclose behavioral traits such as rate limits, authentication requirements, pagination behavior (implied by cursor parameter but not explained), or what the search covers (e.g., text content, hashtags). This leaves significant gaps for a search tool.

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 wasted words. It's appropriately sized and front-loaded, making it easy to scan and understand the core purpose immediately.

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 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral constraints. Given the complexity and lack of structured data, more context is needed to adequately guide an agent.

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%, so the schema fully documents parameters (query, limit, cursor). The description adds no additional meaning beyond what's in the schema, such as query syntax examples or cursor usage details. 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search for posts on Bluesky' clearly states the action (search) and resource (posts), but it's vague about scope and doesn't differentiate from sibling tools like bluesky_search_profiles or bluesky_get_posts. It lacks specificity about what kind of search this performs.

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?

No guidance is provided on when to use this tool versus alternatives like bluesky_search_profiles (for profile search) or bluesky_get_posts (which might retrieve specific posts). The description offers no context about appropriate use cases 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/berlinbra/BlueSky-MCP'

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