Skip to main content
Glama

gmail modify labels

gmail_modify_labels
Idempotent

Add or remove labels on Gmail messages to mark them read, archive, or organize inboxes through label changes.

Instructions

Add or remove labels on a message (e.g. mark read, archive).

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

Input Schema

NameRequiredDescriptionDefault
addNo
removeNo
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, idempotent, non-destructive, open-world mutation, so the safety profile is covered. The description adds useful context via the archive/mark-read examples, but does not disclose what label format is required (IDs vs. names) or what gets returned. Additional context beyond annotations is present but thin.

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?

A single front-loaded sentence with zero filler; the core action leads and the examples follow in parentheses. It is appropriately sized, though brevity comes at the cost of covering the parameters.

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?

With annotations and an output schema present, the definition doesn't need to explain return values or the safety profile. However, for a 3-parameter tool with 0% schema coverage, the missing label-identifier convention is a meaningful gap that an agent would need to resolve by trial or another tool call.

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 0%, so the description carries the full burden, yet it never explains the `add`, `remove`, or `message_id` parameters. An agent must guess whether the label arrays take IDs or display names, which is critical for correct invocation. Only the verb implicitly hints at the add/remove semantics.

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 states a specific verb+resource: 'Add or remove labels on a message,' which an agent can immediately distinguish from siblings like gmail_list_labels or gmail_trash_message. The parenthetical examples ('mark read, archive') reinforce the semantics, though no sibling is named 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?

The examples (mark read, archive) imply the intended use cases, but there is no explicit guidance on when to prefer this tool over alternatives such as gmail_trash_message, nor any prerequisite about needing label identifiers first. Usage is implied rather than stated.

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