gsuite

google-gmail_list_messages

List Gmail messages with filters for search queries, labels, and pagination to retrieve specific emails from your mailbox.

Instructions

List messages in user's mailbox with optional filtering

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": "google-gmail_list_messages"
  }
}

Input Schema

Name	Required	Description
`q`	No	Gmail search query (e.g., 'from:user@example.com subject:important')
`userId`	No	User's email address or 'me' for authenticated user
`labelIds`	No	Comma-separated list of label IDs to filter by
`pageToken`	No	Page token for pagination
`maxResults`	No	Maximum number of messages to return (1-500, default 100)
`includeSpamTrash`	No	Include messages from SPAM and TRASH

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It does not mention that returns only metadata, pagination behavior, or that it is a read operation. Adds minimal value beyond schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Single sentence, concise but overly brief. Lacks structure like sections or bullet points, though front-loaded.

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?

No output schema, yet the description does not indicate return format or that full message content requires separate calls. Incomplete for a tool with 6 parameters.

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 parameters are well-documented. The description adds 'optional filtering' but no new semantic context for individual parameters.

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 uses a specific verb 'List' and resource 'messages in user's mailbox', and mentions filtering. It is clear but does not explicitly distinguish from the sibling 'search_messages' tool.

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 guidance on when to use this tool versus alternatives like 'search_messages'. The description only states what it does without usage context.

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