Skip to main content
Glama
gmail-mcp-server

gmail-mcp-server

by fbassas

search_emails

Find Gmail messages using Gmail search syntax (e.g., 'from:user@example.com is:unread') and return matching emails, with an optional result limit.

Instructions

Cerca correus a Gmail fent servir la sintaxi de cerca de Gmail (p. ex. 'from:algu@exemple.com is:unread').

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

Input Schema

NameRequiredDescriptionDefault
queryYes
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the whole burden. It never says the operation is read-only/non-destructive, does not disclose the default or cap on result count (maxResults default 10, max 50), and says nothing about result shape or pagination.

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 front-loaded sentence with no padding, leading with the verb and resource before the syntax hint. It is terse to the point of thinness, but nothing is wasted.

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 two-parameter read tool with no annotations and no output schema, the description should at least confirm the read-only nature and what the call returns or how many results. Those gaps are left entirely to inference.

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 0%, so description must compensate. It does so well for the required `query` param by naming Gmail search syntax and giving a concrete example ('from:... is:unread'); `maxResults` is left unmentioned, though its bounds and default are stated structurally in the schema.

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?

The description states a specific verb and resource ('Cerca correus a Gmail') and adds the key qualifier that queries use Gmail search syntax. An agent can tell this apart from create_draft, list_labels and read_email without opening any schema, though no sibling is named explicitly.

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?

Usage is only implied: the search-syntax hint signals this is for querying messages, but there is no explicit statement of when to prefer it over read_email or list_labels, and no exclusions (e.g. whether it covers spam/trash or only inbox).

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