Skip to main content
Glama
mikemc
by mikemc

twist_inbox_mark_all_read

Clear your Twist workspace inbox by marking all threads as read. Use this tool to maintain inbox organization and focus on unread messages.

Instructions

Marks all inbox threads in the workspace as read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function implementing the twist_inbox_mark_all_read tool. It retrieves the workspace ID from environment, makes a POST request to Twist API 'inbox/mark_all_read', and returns success or error message.
    def twist_inbox_mark_all_read(
        ctx: Context
    ) -> str:
        """Marks all inbox threads in the workspace as read.
        """
        token = ctx.request_context.lifespan_context.twist_token
    
        workspace_id = os.getenv("TWIST_WORKSPACE_ID")
        if not workspace_id:
            logger.error("TWIST_WORKSPACE_ID environment variable is required")
            return "Error: TWIST_WORKSPACE_ID environment variable is required"
    
        params = {"workspace_id": workspace_id}
    
        try:
            logger.info(f"Marking all inbox threads as read for workspace ID: {workspace_id}")
    
            result = twist_request("inbox/mark_all_read", params=params, token=token, method="POST")
    
            logger.info("Successfully marked all inbox threads as read")
            return "Successfully marked all inbox threads as read"
        except Exception as error:
            logger.error(f"Error marking all inbox threads as read: {error}")
            return f"Error marking all inbox threads as read: {str(error)}"
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 but doesn't mention whether this is reversible, if it requires authentication, potential rate limits, or what happens to archived or muted threads. This leaves significant gaps for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 of a mutation tool (marking all threads as read) with no annotations and no output schema, the description is insufficient. It doesn't explain the return value, error conditions, or side effects, leaving the agent with incomplete information to use the tool effectively.

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 tool has 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add any parameter information, which is appropriate here, but it doesn't compensate for any gaps since there are none to address.

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 ('marks as read') and the resource ('all inbox threads in the workspace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'twist_threads_mark_all_read', which might cause confusion about scope (inbox vs. threads).

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 like 'twist_threads_mark_all_read' or 'twist_inbox_archive_all'. It lacks context about prerequisites, such as whether the user needs specific permissions or if this applies to all inboxes or a specific one.

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