Skip to main content
Glama
mail-mcp-server

mail-mcp-server

search

Find Gmail messages across connected mailboxes using Gmail query syntax and return matching IDs, dates, senders, subjects, and labels, newest first.

Instructions

Find messages with Gmail search syntax. Returns id, date, from, subject and labels, newest first.

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": {
      "mailbox": "<mailbox>",
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoDefault 25, at most 500
queryYesGmail search syntax, e.g. "category:promotions older_than:30d"
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full load, but it does disclose key behavior beyond the schema: read-only search semantics, projection of returned fields (id, date, from, subject, labels), and sort order (newest first). It omits pagination/truncation behavior at 500 results, whether the search touches only that mailbox, and any rate-limit or auth context. Adequate but incomplete for a zero-annotation tool.

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, front-loaded with the action and dialect, followed by return fields and ordering. Nothing redundant or padded.

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 3-parameter, no-annotation, no-output-schema search tool, the description covers purpose, query dialect, returned fields and sort order — enough to call it correctly. Minor gaps: no guidance on choosing this over get_message/get_thread, and no statement about result caps or pagination.

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 100%, so each parameter already has a description including the max default of 25 and the syntax example. The description only reinforces syntax and ordering; it adds no meaning about max interaction with result ordering or what query operators are unsupported.

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 and resource ("Find messages") plus the query dialect ("Gmail search syntax") and the return shape. It does not name or distinguish itself from siblings like get_message, get_thread, or sender_stats, relying only on the generic name "search".

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?

No when-to-use or when-not-to-use guidance. It never says to prefer get_message for fetching a single known message or list_mailboxes to obtain the mailbox argument, and gives no exclusions. The only routing hint is indirect: the mailbox parameter points at list_mailboxes.

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