Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_batch_report_spam

Report multiple emails as spam or junk in one batch call instead of reporting them individually. Accepts up to 1000 email IDs per request across Gmail, Outlook, iCloud, and IMAP accounts.

Instructions

Report multiple emails as spam/junk at once. Much faster than individual 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_report_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdsYesArray of email IDs to report as spam
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when emails are not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not explain what reporting as spam actually does (moves to junk folder, may affect sender/block state), whether already-spam emails cause errors, partial-failure behavior for a batch, or permission/auth requirements.

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?

Two short sentences with the action front-loaded and the efficiency rationale as supporting context. No waste, though the second sentence is closer to marketing than specification.

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 batch mutation tool with no annotations and no output schema, the description should disclose side effects, batch-size limits, and partial-failure semantics. None of these are covered, leaving significant gaps beyond what the schema provides.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is moderate (67%); emailIds and sourceFolder are documented in the schema while accountId is not. The description adds nothing beyond the schema for any parameter, so it does not compensate for the undocumented accountId, leaving this at a baseline level.

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+resource (report emails as spam/junk) and adds batch scope ("multiple... at once"), which lets an agent distinguish it from the singular email_report_spam sibling. The differentiation is implicit via "multiple"/"individual calls" rather than a named alternative.

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?

"Much faster than individual calls" implies when to prefer batching over the single-email tool, which is useful context. However, it gives no when-not conditions, no guidance on the sourceFolder requirement for IMAP/iCloud, and no mention of limits or error handling.

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