Skip to main content
Glama

Coline

Organize mail thread

organize_mail_thread
Idempotent

Archives, marks read or unread, stars or unstars, or labels a mail thread when the person asks. Every change can be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "accountId": "<accountId>",
      "threadId": "<threadId>",
      "action": "<action>"
    },
    "name": "organize_mail_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoFor add_label and remove_label.
actionYes
threadIdYesThread id from list_mail_threads or search_mail.
accountIdYesMail account id from list_mailboxes or a thread.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
doneYes
actionYes
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare that this is a non-destructive, idempotent write, so the bar is lower; the description adds real value by stating "Every change can be undone," which is reversibility context the hints do not express. It does not clarify that add_label/remove_label require the label parameter or what happens when label is omitted, which is a meaningful behavioral gap.

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?

Two short sentences with the action set front-loaded and the reversibility guarantee tucked at the end; nothing is redundant or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a 4-of-5 required schema, and an output schema covering return values, the description is close to sufficient for a simple mutation tool. The one miss is the conditional label requirement for the label actions, which an agent must infer from the schema alone.

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 80%, so the schema already documents workspace, accountId, threadId, label, and the action values. The description's action list merely restates the enum and adds no detail about the conditional dependency between action and label.

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 names the resource (mail thread) and enumerates the specific mutations it performs – archive, mark read/unread, star/unstar, label – which maps directly to the action enum. It clearly separates this from read-oriented siblings like read_mail_thread or show_mail, though it does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"when the person asks" gives a light trigger condition, implying this is a user-initiated action rather than an automated sweep. There is no guidance on when to prefer other tools (e.g., follow_thread, read_mail_thread) or on preconditions such as resolving threadId first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources