Skip to main content
Glama
mikemc
by mikemc

twist_threads_unmute

Restores notifications for a muted conversation thread in Twist workspaces by specifying the thread ID.

Instructions

Unmutes a thread.

Args: id: The id of the thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The main handler function that implements the tool logic: takes thread ID, constructs params, calls twist_request to the 'threads/unmute' API endpoint with POST method, logs actions, and returns the response or error.
    def twist_threads_unmute(
        ctx: Context,
        id: int
    ) -> Union[str, Dict[str, Any]]:
        """Unmutes a thread.
    
        Args:
            id: The id of the thread
        """
        all_params = locals()
        token = ctx.request_context.lifespan_context.twist_token
        params = {k: v for k, v in all_params.items() if k != 'ctx' and v is not None}
    
        try:
            logger.info(f"Unmuting thread with ID: {id}")
            thread_data = twist_request("threads/unmute", params=params, token=token, method="POST")
            logger.info(f"Successfully unmuted thread with ID: {id}")
            return thread_data
        except Exception as error:
            logger.error(f"Error unmuting thread: {error}")
            return f"Error unmuting thread: {str(error)}"
  • main.py:42-48 (registration)
    Dynamic registration of all twist_* functions from src.threads (including twist_threads_unmute) as MCP tools using FastMCP's tool decorator.
    # Register all tools from tool modules
    for module in [src.inbox, src.threads]:
        for name, func in inspect.getmembers(module, inspect.isfunction):
            if name.startswith('twist_') and func.__module__ == module.__name__:
                logger.info(f"Registering tool: {name}")
                mcp.tool()(func)
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 insight. It states the action ('Unmutes') but doesn't disclose side effects, permissions required, rate limits, or what happens if the thread isn't muted. For a mutation tool with zero annotation coverage, this leaves critical gaps in understanding its behavior.

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 action ('Unmutes a thread.') and uses a clear 'Args:' section for parameters. It avoids unnecessary words, but the parameter explanation could be more informative (e.g., 'Thread ID as an integer'). Overall, it's efficient but slightly under-specified.

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 the tool's mutation nature, lack of annotations, no output schema, and low schema coverage (0%), the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, error conditions, or return values. For a tool that alters thread state, this leaves the agent with insufficient context to use it reliably.

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 adds basic semantics for the 'id' parameter ('The id of the thread'), which is helpful since schema description coverage is 0%. However, it doesn't specify format constraints (e.g., integer type, where to find the ID) or provide examples. With only one parameter, the baseline is 4, but the lack of detail reduces it to 3.

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 ('Unmutes') and resource ('a thread'), making the purpose immediately understandable. It distinguishes from siblings like 'twist_threads_mute' by specifying the opposite action. However, it doesn't specify what 'unmuting' entails in this context (e.g., notifications, visibility), which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., the thread must be muted first), contrast with similar tools like 'twist_threads_mute', or explain the effect of unmuting (e.g., restores notifications). The agent must infer usage from the name alone.

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/mikemc/twist-mcp-server'

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