Skip to main content
Glama
berlinbra

BlueSky MCP Server

bluesky_get_posts

Retrieve recent posts from a user on the BlueSky social network using official API integration.

Instructions

Get recent posts from a user

Input Schema

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

Implementation Reference

  • The handler logic for the 'bluesky_get_posts' tool. It retrieves recent posts from the authenticated user's feed using the Bluesky API's get_author_feed method, supporting limit and cursor parameters.
    elif name == "bluesky_get_posts":
        limit = arguments.get("limit", 50)
        cursor = arguments.get("cursor")
        response = await asyncio.to_thread(
            bluesky.client.app.bsky.feed.get_author_feed,
            {'actor': IDENTIFIER, 'limit': limit, 'cursor': cursor}
        )
  • Registration of the 'bluesky_get_posts' tool in the list_tools handler, including its description and input schema definition.
    types.Tool(
        name="bluesky_get_posts",
        description="Get recent posts from a user",
        inputSchema={
            "type": "object",
            "properties": {
                "limit": {
                    "type": "integer",
                    "description": "Maximum number of posts to return (default 50, max 100)",
                    "default": 50,
                },
                "cursor": {
                    "type": "string",
                    "description": "Pagination cursor for next page of results",
                },
            },
        },
    ),
  • Input schema for the 'bluesky_get_posts' tool, defining optional limit (default 50) and cursor parameters.
    inputSchema={
        "type": "object",
        "properties": {
            "limit": {
                "type": "integer",
                "description": "Maximum number of posts to return (default 50, max 100)",
                "default": 50,
            },
            "cursor": {
                "type": "string",
                "description": "Pagination cursor for next page of results",
            },
        },
    },
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. It mentions 'Get recent posts' but fails to describe key traits such as pagination behavior (implied by the cursor parameter but not explained), rate limits, authentication requirements, or error handling. This omission is significant for a tool with parameters and no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, straightforward sentence that efficiently conveys the core action and resource. It is front-loaded with essential information and avoids unnecessary words, making it appropriately concise for its purpose, though it could be more informative.

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 the tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values (e.g., post format, fields), behavioral aspects like pagination, and context for usage relative to siblings. This leaves gaps that could hinder an agent's ability to use the tool effectively.

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 input schema has 100% description coverage, clearly documenting 'limit' and 'cursor' with defaults and purposes. The description adds no additional meaning beyond the schema, such as explaining how 'recent' relates to these parameters. Since schema coverage is high, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 states the basic action ('Get recent posts') and resource ('from a user'), which clarifies the tool's purpose. However, it lacks specificity about what constitutes 'recent' (e.g., time frame, recency criteria) and does not differentiate from sibling tools like 'bluesky_get_personal_feed' or 'bluesky_search_posts', making it vague in context.

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 does not mention scenarios like retrieving a user's posts versus searching posts or accessing a personal feed, nor does it specify prerequisites such as user identification. This leaves the agent without clear usage context.

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