Skip to main content
Glama

send_post

Create and publish posts to Bluesky with text, images, links, mentions, and replies to specific profiles or conversations.

Instructions

Send a post to Bluesky.

Args:
    ctx: MCP context
    text: Text content of the post
    profile_identify: Optional handle or DID. Where to send post. If not provided, sends to current profile
    reply_to: Optional reply reference with 'root' and 'parent' containing 'uri' and 'cid'
    embed: Optional embed object (images, external links, records, or video)
    langs: Optional list of language codes used in the post (defaults to ['en'])
    facets: Optional list of rich text facets (mentions, links, etc.)

Returns:
    Status of the post creation with uri and cid of the created post

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
profile_identifyNo
reply_toNo
embedNo
langsNo
facetsNo

Implementation Reference

  • The handler function for the 'send_post' MCP tool. Decorated with @mcp.tool() for automatic registration and schema inference. Handles creating a Bluesky post using the atproto Client's send_post method with prepared parameters.
    @mcp.tool()
    def send_post(
        ctx: Context,
        text: str,
        profile_identify: Optional[str] = None,
        reply_to: Optional[Dict[str, Any]] = None,
        embed: Optional[Dict[str, Any]] = None,
        langs: Optional[List[str]] = None,
        facets: Optional[List[Dict[str, Any]]] = None,
    ) -> Dict:
        """Send a post to Bluesky.
    
        Args:
            ctx: MCP context
            text: Text content of the post
            profile_identify: Optional handle or DID. Where to send post. If not provided, sends to current profile
            reply_to: Optional reply reference with 'root' and 'parent' containing 'uri' and 'cid'
            embed: Optional embed object (images, external links, records, or video)
            langs: Optional list of language codes used in the post (defaults to ['en'])
            facets: Optional list of rich text facets (mentions, links, etc.)
    
        Returns:
            Status of the post creation with uri and cid of the created post
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            # Prepare parameters for send_post
            kwargs: Dict[str, Any] = {"text": text}
    
            # Add optional parameters if provided
            if profile_identify:
                kwargs["profile_identify"] = profile_identify
    
            if reply_to:
                kwargs["reply_to"] = reply_to
    
            if embed:
                kwargs["embed"] = embed
    
            if langs:
                kwargs["langs"] = langs
    
            if facets:
                kwargs["facets"] = facets
    
            # Create the post using the native send_post method
            post_response = bluesky_client.send_post(**kwargs)
    
            return {
                "status": "success",
                "message": "Post sent successfully",
                "post_uri": post_response.uri,
                "post_cid": post_response.cid,
            }
        except Exception as e:
            error_msg = f"Failed to send 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 for behavioral disclosure. While it states the action ('Send a post') and return value, it doesn't mention authentication requirements, rate limits, error conditions, or whether this is a destructive operation. For a write tool with zero 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 for Args and Returns. Each sentence earns its place by explaining parameter semantics. While efficient, it could be slightly more front-loaded by stating the core purpose more prominently before diving into parameters.

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?

For a write operation with 6 parameters and no annotations or output schema, the description does well on parameters but lacks critical behavioral context. It explains what the tool does and its parameters but doesn't cover authentication, error handling, or operational constraints that would be essential for safe use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing clear semantic explanations for all 6 parameters. Each parameter gets a meaningful description that explains its purpose, optionality, and default behavior (e.g., 'If not provided, sends to current profile', 'defaults to ['en']'), adding substantial value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states the specific action ('Send a post to Bluesky') and resource ('post'), distinguishing it from sibling tools like 'send_image', 'send_video', or 'repost'. It explicitly identifies the core function without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating posts on Bluesky but provides no explicit guidance on when to use this versus alternatives like 'send_image' or 'repost'. It mentions optional parameters but doesn't explain scenarios where they're appropriate or when other tools might be better suited.

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