Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_batch_label

Apply or remove labels on up to 1,000 Gmail emails in a single call. Batch labeling avoids repeated individual requests when organizing large groups of messages.

Instructions

Add or remove labels on multiple emails at once (Gmail only). Much faster than individual email_label calls.

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": {
      "accountId": "<accountId>",
      "emailIds": "<emailIds>"
    },
    "name": "email_batch_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdsYesArray of email IDs to label
accountIdYes
addLabelsNo
removeLabelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important platform restriction (Gmail only) and that the operation both applies and removes labels, i.e. it is mutating. It does not say whether label removal is reversible, what permissions are needed, whether partial failures across a 1000-item batch are reported, or what at least one of addLabels/removeLabels being required means in practice.

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 operation and platform scope front-loaded and the sibling comparison immediately after. No filler or redundant restatement of the name.

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?

Enough to know what the tool does and when to prefer it over the single-email variant, but for a 4-parameter mutating batch tool with no annotations, no output schema, and sparse schema descriptions, it leaves meaningful gaps: parameter meanings, batch limits, and failure behavior.

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 emailIds is documented. The description says nothing about accountId, addLabels, removeLabels, or the key behavioral rule that at least one of add/remove must be supplied. For a low-coverage schema, the description needed to compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair ('add or remove'), the resource ('labels'), the batch scope ('multiple emails at once'), and a platform constraint ('Gmail only'). It also names the sibling it supersedes ('individual email_label calls'), so an agent can distinguish it from email_label without opening either schema.

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

Usage Guidelines4/5

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

The comparison to individual email_label calls gives clear implied guidance: use this when touching more than one email. It does not state explicit exclusions (e.g. 'for a single email use email_label') or prerequisites such as required label IDs already existing, so it falls short of full when/when-not coverage.

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