Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Update message labels

update_message
Idempotent

Add or remove free-string labels on an email message to manage a triage work-queue, so processed mail is not reprocessed.

Instructions

Add or remove free-string labels on a message (the triage work-queue, so processed mail is not reprocessed).

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>",
      "message_id": "<message_id>"
    },
    "name": "update_message"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive), so the bar is lower. The description adds that labels are free-form strings and serve as a processing marker, but it does not say whether an unknown label string is created on the fly, whether add and remove can be combined in one call, or what happens on an unknown message_id.

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 sentence with the action front-loaded and the rationale appended. Nothing is wasted and nothing needs to be moved forward.

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 tool with annotations covering only safety, the description covers label semantics but omits the message_id source, mutation ordering, and error behavior on unknown labels or ids. Adequate to start, incomplete for confident invocation.

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?

Schema description coverage is only 25% (only inbox_id is documented), so the description must compensate. It does add real meaning by clarifying that labels are 'free-string' rather than ids, which directly informs add_labels and remove_labels. It still leaves message_id and the add/remove interaction unexplained, but the label-type clarification is substantive.

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 gives a specific verb pair and resource: 'Add or remove free-string labels on a message.' It also states the operational intent (triage work-queue). It does not explicitly distinguish itself from update_thread or update_label, but the resource is unambiguous enough to select it.

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?

The parenthetical 'the triage work-queue, so processed mail is not reprocessed' implies when this tool is useful, but it never states when-not to use it or which sibling to prefer for threading or label-definition changes. Guidance is implied rather than explicit.

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