Skip to main content
Glama
berlinbra

BlueSky MCP Server

by berlinbra
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

bluesky_get_personal_feed

Retrieve your personalized Bluesky feed with pagination support to view posts from followed accounts.

Instructions

Get your personalized Bluesky feed

Input Schema

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

Implementation Reference

  • src/bluesky_mcp/server.py:246-252 (handler)
    Handler logic for the 'bluesky_get_personal_feed' tool. Extracts limit and cursor parameters, then calls the Bluesky API's get_timeline method to fetch the personalized feed.
    elif name == "bluesky_get_personal_feed":
    limit = arguments.get("limit", 50)
    cursor = arguments.get("cursor")
    response = await asyncio.to_thread(
        bluesky.client.app.bsky.feed.get_timeline,
        {'limit': limit, 'cursor': cursor}
    )
  • src/bluesky_mcp/server.py:142-159 (registration)
    Registration of the 'bluesky_get_personal_feed' tool, including its name, description, and input schema definition for limit and cursor parameters.
    types.Tool(
    name="bluesky_get_personal_feed",
    description="Get your personalized Bluesky feed",
    inputSchema={
        "type": "object",
        "properties": {
            "limit": {
                "type": "integer",
                "description": "Maximum number of feed items to return (default 50, max 100)",
                "default": 50,
            },
            "cursor": {
                "type": "string",
                "description": "Pagination cursor for next page of results",
            },
        },
    },
),
  • src/bluesky_mcp/server.py:145-158 (schema)
    Input schema definition for the 'bluesky_get_personal_feed' tool, specifying optional limit (default 50) and cursor parameters.
    inputSchema={
    "type": "object",
    "properties": {
        "limit": {
            "type": "integer",
            "description": "Maximum number of feed items to return (default 50, max 100)",
            "default": 50,
        },
        "cursor": {
            "type": "string",
            "description": "Pagination cursor for next page of results",
        },
    },
},

Tool Definition Quality

C2.9/5.0
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. It states the action ('Get') but lacks details on authentication needs, rate limits, pagination behavior (implied by 'cursor' but not explained), or what 'personalized' entails. This is a significant gap for a tool that likely requires user context.

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 no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand 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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'personalized' means (e.g., based on follows, algorithms), authentication requirements, or return format. For a feed-fetching tool with user context, this leaves critical gaps.

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 both parameters ('limit' and 'cursor') with descriptions and defaults. The description adds no additional parameter information beyond what the schema provides, which is acceptable given the high coverage.

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 verb ('Get') and resource ('your personalized Bluesky feed'), making the purpose understandable. However, it doesn't explicitly differentiate from siblings like 'bluesky_get_posts' or 'bluesky_search_posts', which might also retrieve posts but with different scopes or filters.

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. It doesn't mention prerequisites (e.g., authentication), context for 'personalized' feed, or how it differs from sibling tools like 'bluesky_get_posts' or 'bluesky_search_posts'.

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