Skip to main content
Glama
mikemc
by mikemc

twist_threads_remove

Delete a thread from Twist workspaces by specifying its ID to manage your inbox content.

Instructions

Removes a thread.

Args: id: The id of the thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function implementing the 'twist_threads_remove' tool. It takes a thread ID and sends a POST request to the Twist API 'threads/remove' endpoint to remove the thread.
    def twist_threads_remove(
        ctx: Context,
        id: int
    ) -> str:
        """Removes 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"Removing thread with ID: {id}")
            twist_request("threads/remove", params=params, token=token, method="POST")
            logger.info(f"Successfully removed thread with ID: {id}")
            return f"Successfully removed thread with ID: {id}"
        except Exception as error:
            logger.error(f"Error removing thread: {error}")
            return f"Error removing thread: {str(error)}"
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. It states the tool 'Removes a thread' but doesn't clarify if this is permanent deletion, reversible, requires specific permissions, or has side effects (e.g., impact on related data). This leaves significant behavioral gaps 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 concise and front-loaded with the main action, followed by a brief parameter explanation. It avoids unnecessary words, though the structure could be slightly improved by integrating the parameter note more seamlessly.

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 complexity as a mutation operation with no annotations, no output schema, and incomplete parameter guidance, the description is inadequate. It fails to address critical aspects like permanence, permissions, or error handling, leaving the agent with insufficient context for safe invocation.

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 minimal semantics beyond the input schema: it specifies that 'id' is 'The id of the thread'. With 0% schema description coverage and only one parameter, this provides basic context, but doesn't elaborate on format, constraints, or examples, keeping it at the baseline for low coverage.

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 ('Removes') and resource ('a thread'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'twist_threads_move_to_channel' or 'twist_threads_archive' operations, which might also remove threads in different contexts.

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. With siblings like 'twist_threads_move_to_channel', 'twist_threads_archive', and 'twist_inbox_archive', it's unclear whether this is a permanent deletion, archiving, or something else, and no prerequisites or exclusions are mentioned.

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