Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_report_spam

Report an email as spam to train the provider's own junk filter and improve future filtering; unlike deletion, it sends the same signal as the Report Junk button.

Instructions

Report an email as spam/junk, training the provider's own spam filter (the same signal the "Report Junk" button sends in Gmail/Outlook). This is different from email_delete, which removes the message but teaches the filter nothing. Not an abuse report to the provider's security team — it only trains this account's filter.

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_report_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key non-obvious side effect: it trains a per-account spam filter rather than deleting or escalating. It also scopes the effect to 'this account's filter.' It does not say whether the message is moved to a junk folder, whether the action is reversible, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: the action first, then the discriminating comparison, then the negative scope. Every sentence adds information an agent needs and nothing is repeated from structured fields.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with no annotations and no output schema, the description covers purpose, side effect, and boundaries well. The remaining gaps are the return/response behavior and the parameter meanings, which are not covered anywhere else.

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 33%, so the description should compensate, but it says nothing about any of the three parameters. Only sourceFolder carries a schema description (the IMAP/iCloud non-INBOX case); accountId and emailId are undocumented in both places, and the description gives no hint about how to obtain them.

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 and resource ('Report an email as spam/junk') and immediately qualifies the scope: it trains the provider's own filter, mirroring the Gmail/Outlook 'Report Junk' button. It explicitly separates itself from email_delete and from an abuse report, so an agent can distinguish it from siblings without opening any 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?

Gives explicit when-to-use framing ('the same signal the Report Junk button sends') and two clear when-not-to-use exclusions: use email_delete if you want removal without training, and don't expect this to reach a security team. It does not address what to do when multiple messages need reporting, leaving a real routing decision unstated.

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