Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Update thread labels

update_thread
Idempotent

Add or remove custom labels across an entire email thread to organize and filter messages consistently.

Instructions

Add or remove free-string labels across a whole thread.

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": {
      "inbox_id": "<inbox_id>",
      "thread_id": "<thread_id>"
    },
    "name": "update_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.
thread_idYes
add_labelsNo
remove_labelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds only the thread-wide application scope; it says nothing about what happens to labels that don't exist, whether add and remove can be combined in one call, or auth requirements.

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?

A single short sentence with the operation and scope front-loaded and zero filler; nothing could be removed without losing meaning.

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

Completeness3/5

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

For a 4-parameter mutation with no output schema, the description is minimal but the annotations carry the idempotency and non-destructive guarantees. It still leaves gaps on label validation, combined add/remove behavior, and what the call returns.

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 only 25% — only inbox_id is documented. The description adds the useful detail that labels are 'free-string', implying values are not restricted to predefined IDs, but it leaves thread_id, add_labels and remove_labels format and interaction semantics (e.g., can both be supplied at once) unexplained.

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 a specific verb pair (add/remove) and the resource (labels) plus its scope (across a whole thread), so an agent can tell this apart from update_label or update_message. It does not explicitly contrast with siblings, keeping it below a 5.

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?

There is no when-to-use guidance at all: nothing says when to label a thread versus relabel an existing label via update_label, and no prerequisites (e.g., label must already exist in the inbox) are stated. The agent must infer usage entirely from the name.

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