Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_label

Add or remove Gmail labels on a specific email to categorize messages or update their status.

Instructions

Add or remove labels on an email (Gmail only)

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>",
      "emailId": "<emailId>"
    },
    "name": "email_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
addLabelsNo
removeLabelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the Gmail-only constraint, but not whether labels must already exist, what happens to invalid labels, whether removal is destructive, or what permissions are needed.

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 compact sentence with the action front-loaded and the platform constraint trailing. It is tight, but the brevity is under-specification rather than economy.

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

Completeness2/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 annotations, no output schema, and zero schema coverage, one sentence is insufficient. Critical unknowns — label identifier format, error behavior, and account scoping — are left entirely to inference.

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 must explain all four parameters. It only hints at addLabels/removeLabels through "add or remove labels" and says nothing about whether values are label IDs or display names, nor what accountId and emailId identify.

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?

States a specific verb pair and resource ("Add or remove labels on an email"), which tells the agent exactly what changes and to what object. The singular "an email" implicitly separates it from email_batch_label, though it never names the sibling.

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?

The only usage signal is the parenthetical "(Gmail only)", which is a precondition rather than when-to-use guidance. Nothing tells the agent when to prefer this over email_batch_label or how it relates to email_get_labels for resolving label names.

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