Skip to main content
Glama
mikemc
by mikemc

twist_threads_move_to_channel

Move a thread from one channel to another in Twist workspaces to reorganize discussions and maintain organized communication channels.

Instructions

Moves the thread to a different channel.

Args: id: The id of the thread to_channel: The target channel's id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
to_channelYes

Implementation Reference

  • The handler function that executes the logic to move a Twist thread to a different channel by calling the Twist API endpoint 'threads/move_to_channel'.
    def twist_threads_move_to_channel(
        ctx: Context,
        id: int,
        to_channel: int
    ) -> str:
        """Moves the thread to a different channel.
    
        Args:
            id: The id of the thread
            to_channel: The target channel's id
        """
        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"Moving thread with ID: {id} to channel: {to_channel}")
            twist_request("threads/move_to_channel", params=params, token=token, method="POST")
            logger.info(f"Successfully moved thread with ID: {id} to channel: {to_channel}")
            return f"Successfully moved thread with ID: {id} to channel: {to_channel}"
        except Exception as error:
            logger.error(f"Error moving thread: {error}")
            return f"Error moving thread: {str(error)}"
  • main.py:42-48 (registration)
    Dynamic registration loop that registers all functions starting with 'twist_' from src.threads (including twist_threads_move_to_channel) as MCP tools using FastMCP.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 the full burden of behavioral disclosure. It states the action ('Moves') but doesn't describe effects (e.g., whether it preserves thread history, affects notifications, or requires specific permissions), error conditions, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 with the core purpose in the first sentence. The parameter explanations are brief and relevant, though the structure could be improved by integrating usage context rather than listing args separately.

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, no output schema, and low schema description coverage, the description is incomplete. It lacks details on behavioral effects, error handling, permissions, and how it interacts with sibling tools, leaving significant gaps for an AI agent to infer correct usage.

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 basic meaning by naming parameters ('id' for the thread, 'to_channel' for the target) and implies their roles, but doesn't specify format details (e.g., integer ranges) or constraints beyond what the schema's types indicate. This provides marginal value over the bare schema.

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 ('Moves') and resource ('the thread'), specifying what the tool does. It distinguishes from siblings like 'twist_threads_get' or 'twist_threads_update' by focusing on relocation, but doesn't explicitly differentiate from similar tools like 'twist_threads_remove' or 'twist_threads_pin' in terms of purpose.

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., thread must exist, user must have permissions), exclusions (e.g., cannot move to archived channels), or related tools like 'twist_threads_update' for other modifications.

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