Skip to main content
Glama
mikemc
by mikemc

twist_threads_unstar

Remove a thread from your starred items in Twist to clean up your workspace and focus on current priorities.

Instructions

Unstars a thread.

Args: id: The id of the thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The main handler function for the 'twist_threads_unstar' tool. It takes a thread ID, constructs parameters, and calls the Twist API endpoint 'threads/unstar' via twist_request to unstar the thread. Handles logging and errors appropriately.
    def twist_threads_unstar(
        ctx: Context,
        id: int
    ) -> str:
        """Unstars 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"Unstarring thread with ID: {id}")
            twist_request("threads/unstar", params=params, token=token, method="POST")
            logger.info(f"Successfully unstarred thread with ID: {id}")
            return f"Successfully unstarred thread with ID: {id}"
        except Exception as error:
            logger.error(f"Error unstarring thread: {error}")
            return f"Error unstarring thread: {str(error)}"
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. It states the action ('Unstars') but doesn't mention permissions required, whether the change is reversible, error conditions, or what happens if the thread isn't starred. This is a significant gap 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 appropriately brief with a clear main sentence followed by parameter documentation. The two-sentence structure is efficient, though the Args formatting could be slightly more integrated with the main description.

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 and no output schema, the description is insufficient. It doesn't explain what 'unstarring' means in this context, what the expected outcome is, or any behavioral details. The parameter documentation helps but doesn't compensate for the overall lack of context.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context for the single parameter by specifying 'The id of the thread' in the Args section. With 0% schema description coverage and only one parameter, this adequately compensates and provides necessary semantic information beyond the basic 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 ('Unstars') and the resource ('a thread'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its sibling 'twist_threads_star' or other thread manipulation tools, 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. It doesn't mention the sibling 'twist_threads_star' for starring threads, nor does it explain prerequisites like needing a starred thread first. Usage context is implied but not stated.

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