Skip to main content
Glama

get_posts

Retrieve multiple Bluesky posts by specifying their URIs to access content directly from the Bluesky Social MCP server.

Instructions

Get multiple posts by their URIs.

Args:
    ctx: MCP context
    uris: List of post URIs to retrieve

Returns:
    List of requested posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the get_posts tool logic. It fetches multiple posts using the Bluesky client given a list of URIs.
    @mcp.tool()
    def get_posts(
        ctx: Context,
        uris: List[str],
    ) -> Dict:
        """Get multiple posts by their URIs.
    
        Args:
            ctx: MCP context
            uris: List of post URIs to retrieve
    
        Returns:
            List of requested posts
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            posts_response = bluesky_client.get_posts(uris)
    
            # Convert the response to a dictionary
            if hasattr(posts_response, "model_dump"):
                posts_data = posts_response.model_dump()
            else:
                posts_data = posts_response
    
            return {"status": "success", "posts": posts_data}
        except Exception as e:
            error_msg = f"Failed to get posts: {str(e)}"
            return {"status": "error", "message": error_msg}
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves posts by URIs but lacks behavioral details such as error handling (e.g., invalid URIs), rate limits, authentication requirements, or whether it's read-only. The mention of 'ctx: MCP context' is vague and adds little value.

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 front-loaded with the core purpose, followed by structured sections for args and returns. It's efficient with minimal waste, though the 'ctx' parameter could be omitted or better explained to improve clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 low schema coverage, the description is moderately complete. It covers the basic operation and parameters but lacks details on behavior, error cases, and output structure. For a tool with 1 parameter and many siblings, it should provide more context to guide usage 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?

Schema description coverage is 0%, so the description must compensate. It documents the 'uris' parameter as a list of post URIs to retrieve, which adds meaning beyond the schema's basic type definition. However, it doesn't specify URI format, constraints, or examples, leaving gaps in understanding.

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 a specific verb ('Get') and resource ('posts'), specifying retrieval by URIs. It distinguishes from siblings like 'get_post' (singular) and 'get_author_feed' (by author), but could be more explicit about how it differs from 'get_post_thread' or 'get_timeline'.

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 explicit guidance on when to use this tool versus alternatives like 'get_post' (for single posts) or 'get_author_feed' (for posts by author). The description implies usage for multiple URIs, but lacks context on prerequisites, limitations, or comparisons with sibling tools.

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