Skip to main content
Glama

gmail_search

Read-onlyIdempotent

Search Gmail messages in a connected mailbox by query, with pagination and limits to retrieve specific messages.

Instructions

Search Gmail messages in the connected mailbox.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gmail_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMessages to return (max 100, default 10)
queryNoGmail search query, such as from:alice newer_than:7d
page_tokenNoGmail page token from a previous response
access_tokenNoGmail access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the scope ('connected mailbox') which is minor context, and does not discuss pagination, rate limits, or result format.

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?

The description is a single, waste-free sentence that front-loads the core purpose. It is appropriately concise, though it could be slightly more structured to include a usage cue.

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?

Given the low complexity, rich schema coverage, and strong annotations, the description is nearly complete for an agent to call the tool. It could be improved by explicitly distinguishing this from gmail_read or email_search, but no essential behavioral or parameter information is missing.

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 description coverage is 100%, so all four parameters are documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides, which is the baseline for high coverage.

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 names a specific verb ('Search') and resource ('Gmail messages') and adds scope ('connected mailbox'). It is clear what the tool does, but it does not explicitly differentiate from siblings like gmail_read or email_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?

There is no guidance on when to use this tool versus alternatives such as gmail_read (for reading a specific message) or email_search (for broader email search). The description only implies usage from the verb 'search' with no exclusions or routing hints.

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