Skip to main content
Glama
Sign In
email-mcp

email-mcp

by swapnilsurdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

mark_email

Mark an email as read or unread. Operates across multiple accounts but respects folder protection for trash and deleted items.

Instructions

Mark a message read or unread. Refused (folder_protected) for messages in a protected folder — Trash/Bin/Deleted * by default, plus security.protected_folders.

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": {
      "message_id": "<message_id>",
      "read": "<read>"
    },
    "name": "mark_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes
readYes
accountNo
foldersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool may be refused for protected folders, which is a key behavioral trait. However, it does not mention other side effects like notifications or permanence.

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?

The description is two sentences, concise and front-loaded with the core purpose. No superfluous information.

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?

Given no annotations, no output schema, and 0% schema description coverage, the tool definition is incomplete. It fails to explain the role of the 'account' and 'folders' parameters, leaving important usage aspects unclear.

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 coverage is 0%, yet the description does not explain the four parameters (message_id and read are self-explanatory, but account and folders are ambiguous). The description should provide more detail on optional parameters.

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?

The description clearly states the tool marks a message read or unread, using a specific verb and resource. It distinguishes from siblings like move_email and send_email.

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 description mentions that the tool is refused for messages in protected folders (Trash/Bin/Deleted, plus security.protected_folders), providing a clear when-not-to-use condition. However, it does not explicitly state when to use this tool over alternatives like move_email.

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

Deploy Server

Other Tools