Skip to main content
Glama

unlike_post

Remove a like from a post on Bluesky Social by providing the like URI to undo previous engagement.

Instructions

Unlike a previously liked post.

Args:
    ctx: MCP context
    like_uri: URI of the like.

Returns:
    Status of the unlike operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
like_uriYes

Implementation Reference

  • Full implementation of the unlike_post tool handler. The @mcp.tool() decorator registers it with FastMCP. Takes a like_uri parameter and calls the Bluesky client's unlike method, returning success or error status.
    @mcp.tool()
    def unlike_post(
        ctx: Context,
        like_uri: str,
    ) -> Dict:
        """Unlike a previously liked post.
    
        Args:
            ctx: MCP context
            like_uri: URI of the like.
    
        Returns:
            Status of the unlike operation
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
            bluesky_client.unlike(like_uri)
            return {
                "status": "success",
                "message": "Post unliked successfully",
            }
        except Exception as e:
            error_msg = f"Failed to unlike 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 offers minimal behavioral context. It mentions the operation returns a 'Status' but doesn't specify what that entails (e.g., success/failure indicators, error conditions, or side effects like notifications). For a mutation tool, this is inadequate.

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 appropriately brief and front-loaded with the core purpose. The Args/Returns sections are structured but could be more integrated; however, every sentence contributes without waste.

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 no annotations, no output schema, and a mutation tool with behavioral implications, the description is incomplete. It lacks details on permissions, error handling, return values, and how it interacts with sibling tools like 'get_likes' or 'like_post'.

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 'like_uri' parameter but only states it's the 'URI of the like' without explaining format, source, or how to obtain it. This adds some meaning but doesn't fully address the coverage gap.

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 action ('Unlike') and target ('a previously liked post'), providing specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'unrepost' or 'delete_post', which would require a 5.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., the post must be currently liked) or contrast with similar tools like 'delete_post' or 'unrepost'.

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