Skip to main content
Glama
mikemc
by mikemc

twist_threads_star

Mark a thread as important in Twist workspaces by starring it for easy reference and prioritization.

Instructions

Stars a thread.

Args: id: The id of the thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The main handler function that implements the 'twist_threads_star' tool. It takes a thread ID, extracts parameters, retrieves the Twist API token from context, and makes a POST request to the Twist API endpoint 'threads/star' to star the thread.
    def twist_threads_star(
        ctx: Context,
        id: int
    ) -> str:
        """Stars 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"Starring thread with ID: {id}")
            twist_request("threads/star", params=params, token=token, method="POST")
            logger.info(f"Successfully starred thread with ID: {id}")
            return f"Successfully starred thread with ID: {id}"
        except Exception as error:
            logger.error(f"Error starring thread: {error}")
            return f"Error starring thread: {str(error)}"
  • main.py:42-48 (registration)
    Dynamic registration code that discovers and registers all functions starting with 'twist_' from the src.threads module (among others) as MCP tools using the 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 full burden for behavioral disclosure. 'Stars a thread' implies a mutation/write operation but doesn't specify permissions needed, whether the action is reversible, rate limits, or what happens if the thread is already starred. This leaves significant behavioral questions unanswered.

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 concise with two sentences that directly address the tool's purpose and parameter. However, the structure could be improved by front-loading more critical information rather than separating the parameter explanation into a separate 'Args' section.

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 0% schema description coverage, the description is inadequate. It doesn't explain what 'starring' means in this context, what the expected outcome is, or provide any error handling context. The agent would have significant gaps in understanding how to use this tool effectively.

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

Parameters2/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. While it mentions the 'id' parameter, it provides no semantic context about what constitutes a valid thread ID, where to find it, or format requirements. The description adds minimal value beyond what's already evident from the schema structure.

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 ('Stars') and resource ('a thread'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'twist_threads_unstar' or 'twist_threads_pin', which would be needed for 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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for thread operations (like unstar, pin, mute), but no indication of when this specific star action is appropriate or what prerequisites might exist.

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