Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_modify

Mark Gmail messages as read or unread, star, archive, trash, or apply and remove labels to organize your inbox.

Instructions

Organize messages: mark read/unread, star, archive, move to trash, or add/remove labels. Label names or IDs accepted.

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": {
      "messageIds": "<messageIds>",
      "action": "<action>"
    },
    "name": "gmail_modify"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
addLabelsNo
messageIdsYes
removeLabelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. Trash being listed does not contradict destructiveHint=false since untrash exists, but the description adds no behavioral context beyond annotations: it does not say whether operations apply in bulk to every supplied ID, whether trash is reversible, or how partial failures are reported. A 3 reflects modest added value against an already-annotated tool.

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 compact sentences, capability front-loaded, with the label-format note placed after the operation list. There is no filler or repetition; every clause earns its place.

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 four-parameter mutation tool with no output schema and 0% schema coverage, the definition covers the surface operations but leaves key call-shaping details implicit: bulk semantics of messageIds, which parameters each action requires, and what the caller gets back. Adequate to invoke simple actions, incomplete for ambiguous ones.

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, and it only partially meets it. 'Label names or IDs accepted' usefully clarifies the addLabels/removeLabels value format, but messageIds (a batch array with minItems 1) and the dependency between action='labels' and the add/remove label arrays are left 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 opens with a specific verb and resource ('Organize messages') and enumerates the concrete operations: mark read/unread, star, archive, trash, and label changes. That is enough for an agent to distinguish it from read-only siblings like gmail_read_message or gmail_search. It falls short of a 5 only because it omits two enum actions (moveToInbox, untrash) and never explicitly contrasts itself with a sibling.

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 action list implies the tool's domain, but there is no explicit when-to-use guidance, no prerequisite like 'obtain messageIds from gmail_search first', and no statement about when a different sibling is preferable. Usage is inferable from the enumerated operations rather than stated.

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