Skip to main content
Glama
mikemc
by mikemc

twist_threads_mute

Mute a Twist thread temporarily by specifying its ID and duration in minutes to reduce notifications.

Instructions

Mutes a thread for a number of minutes.

Args: id: The id of the thread minutes: The number of minutes to mute the thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
minutesYes

Implementation Reference

  • Handler function that executes the tool logic: mutes a specified thread for a given number of minutes by making a POST request to the Twist API 'threads/mute' endpoint.
    def twist_threads_mute(
        ctx: Context,
        id: int,
        minutes: int
    ) -> Union[str, Dict[str, Any]]:
        """Mutes a thread for a number of minutes.
    
        Args:
            id: The id of the thread
            minutes: The number of minutes to mute 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"Muting thread with ID: {id} for {minutes} minutes")
            thread_data = twist_request("threads/mute", params=params, token=token, method="POST")
            logger.info(f"Successfully muted thread with ID: {id}")
            return thread_data
        except Exception as error:
            logger.error(f"Error muting thread: {error}")
            return f"Error muting thread: {str(error)}"
  • main.py:42-48 (registration)
    Dynamic registration loop that registers all functions starting with 'twist_' from src.inbox and src.threads modules as MCP tools, including twist_threads_mute.
    # 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action (muting) and parameters but doesn't explain what muting entails (e.g., does it hide notifications, mark as read, affect other users?), whether it's reversible, requires permissions, or has side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 sized and front-loaded: the first sentence states the core purpose, followed by a brief parameter list. There's no wasted text, and it's structured for quick comprehension. However, the 'Args:' section could be integrated more smoothly, and it lacks additional context that might be necessary for completeness.

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 complexity (a mutation tool with 2 parameters), no annotations, and no output schema, the description is incomplete. It covers the basic action and parameters but misses behavioral details (e.g., what muting does, error conditions, return values), usage context, and differentiation from siblings. For a tool that modifies thread state, this level of detail is insufficient.

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 adds meaning by explaining 'id' as 'The id of the thread' and 'minutes' as 'The number of minutes to mute the thread', which clarifies the purpose of each parameter beyond the schema's basic types. However, it doesn't provide details like valid ranges for 'minutes' or format for 'id', leaving some gaps. This partial compensation earns a baseline score.

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: 'Mutes a thread for a number of minutes.' This is a specific verb+resource combination (mute + thread). However, it doesn't explicitly differentiate from sibling tools like 'twist_threads_unmute' or 'twist_threads_mark_unread', which could be related but distinct actions. The purpose is clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'twist_threads_unmute' for reversing the action, 'twist_threads_mark_unread' for similar notification control, or other thread management tools. There's no context on prerequisites, timing, or exclusions, leaving usage unclear.

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