Skip to main content
Glama

mute_user

Block unwanted content by muting specific users on Bluesky Social. This tool allows you to hide posts from selected accounts to customize your feed experience.

Instructions

Mute a user.

Args:
    ctx: MCP context
    actor: Handle or DID of the user to mute

Returns:
    Status of the mute operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorYes

Implementation Reference

  • The main handler function for the 'mute_user' tool. It is decorated with @mcp.tool() for registration in the MCP framework. The function takes a context and actor (handle or DID), authenticates a Bluesky client, calls the client's mute method, and returns success or error status.
    @mcp.tool()
    def mute_user(
        ctx: Context,
        actor: str,
    ) -> Dict:
        """Mute a user.
    
        Args:
            ctx: MCP context
            actor: Handle or DID of the user to mute
    
        Returns:
            Status of the mute operation
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            # The mute method returns a boolean
            success = bluesky_client.mute(actor)
    
            if success:
                return {
                    "status": "success",
                    "message": f"Muted user {actor}",
                }
            else:
                return {
                    "status": "error",
                    "message": "Failed to mute user",
                }
        except Exception as e:
            error_msg = f"Failed to mute user: {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, the description carries full burden but provides minimal behavioral insight. It mentions a 'Status' return but doesn't detail what that entails (e.g., success/failure, error conditions). It lacks information on permissions required, side effects (e.g., does muting affect notifications?), or reversibility, which is critical for a mutation tool.

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 ('Mute a user.'), followed by structured sections for Args and Returns. It avoids unnecessary verbosity, though the 'ctx' parameter in Args is redundant for the agent and could be omitted for better clarity.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain the return value 'Status' in detail, potential errors, or the operational impact of muting. Given the complexity of user management actions, more context on behavior and outcomes is needed for safe and effective use.

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

Parameters4/5

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

The description adds meaningful context for the single parameter 'actor', specifying it as a 'Handle or DID of the user to mute', which clarifies the expected format beyond the schema's generic 'string' type. With 0% schema description coverage and only one parameter, this adequately compensates, though it could note if 'actor' must be a valid, existing user.

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 ('Mute') and target ('a user'), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'unmute_user' beyond the obvious directionality, nor does it specify what 'mute' entails in this context (e.g., hiding posts, preventing interactions).

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 like 'unfollow_user' or 'block_user' (if available), nor does it mention prerequisites such as authentication status. The presence of 'unmute_user' as a sibling implies a toggle relationship, but this isn't explicitly stated.

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