Skip to main content
Glama

get_post

Retrieve a specific Bluesky post using its record key and author identifier to access content directly.

Instructions

Get a specific post.

Args:
    ctx: MCP context
    post_rkey: The record key of the post
    profile_identify: Handle or DID of the post author
    cid: Optional CID of the post

Returns:
    The requested post

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_rkeyYes
profile_identifyNo
cidNo

Implementation Reference

  • The main handler function for the 'get_post' tool. It is registered via the @mcp.tool() decorator and implements the logic to fetch a specific Bluesky post by record key, author identifier, and optional CID using the atproto Client. Returns success with post data or error.
    @mcp.tool()
    def get_post(
        ctx: Context,
        post_rkey: str,
        profile_identify: Optional[str] = None,
        cid: Optional[str] = None,
    ) -> Dict:
        """Get a specific post.
    
        Args:
            ctx: MCP context
            post_rkey: The record key of the post
            profile_identify: Handle or DID of the post author
            cid: Optional CID of the post
    
        Returns:
            The requested post
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            post_response = bluesky_client.get_post(post_rkey, profile_identify, cid)
    
            # Convert the response to a dictionary
            if hasattr(post_response, "model_dump"):
                post_data = post_response.model_dump()
            else:
                post_data = post_response
    
            return {"status": "success", "post": post_data}
        except Exception as e:
            error_msg = f"Failed to get post: {str(e)}"
            return {"status": "error", "message": error_msg}
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 provides minimal behavioral information. It mentions it returns 'The requested post' but doesn't describe error conditions, authentication requirements, rate limits, or what happens when parameters don't match. For a read operation with no annotation coverage, this leaves significant behavioral gaps.

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 well-structured with clear sections (Args, Returns) and front-loads the core purpose. However, the 'ctx: MCP context' in Args is unnecessary clutter since MCP context is implicit in all tools, and the Returns section 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?

For a tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain error cases, authentication requirements, or what the return structure looks like. The parameter documentation helps but doesn't compensate for the lack of behavioral and output information needed for proper tool invocation.

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 provides parameter documentation in the Args section, explaining post_rkey as 'The record key of the post', profile_identify as 'Handle or DID of the post author', and cid as 'Optional CID of the post'. With 0% schema description coverage, this adds meaningful semantic context beyond the bare schema, though it doesn't fully explain parameter relationships or constraints.

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 'Get a specific post' - a specific verb (Get) and resource (post). It distinguishes from siblings like get_posts (plural) and get_post_thread by focusing on a single post. However, it doesn't explicitly mention how it differs from get_author_feed or get_timeline which might also retrieve posts.

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. With siblings like get_posts, get_post_thread, get_author_feed, and get_timeline that all retrieve post data, there's no indication of when this single-post retrieval is preferred over batch retrieval or thread 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/gwbischof/bluesky-social-mcp'

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