Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

gmail_messages_list

Read-only

List Gmail messages matching a search query to find specific emails by sender, subject, or labels. Filter results by user ID, label IDs, and maximum number returned.

Instructions

List Gmail messages matching a query.

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": {
      "userId": "<userId>"
    },
    "name": "gmail_messages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoGmail search query (e.g. "from:user@example.com subject:hello")
userIdYesUser ID (use 'me')
labelIdsNoLabel IDs to filter by
maxResultsNoMax messages to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. Beyond that the description adds nothing: it does not say whether results are paginated, how they are ordered, what happens when the query is empty, or how large result sets are truncated.

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?

It is a single front-loaded sentence with zero redundant wording. The brevity is efficient but tips into under-specification rather than earning its place through density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with full schema coverage and existing annotations, this is minimally adequate. It omits result-shape and pagination context, which matters because there is no output schema to fall back on.

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% — every parameter including the Gmail query syntax example, the 'me' userId convention, labelIds, and maxResults is documented in the schema itself. The description adds no additional meaning, so the baseline of 3 applies.

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 (list) and resource (Gmail messages) and adds the query-filtering scope, so an agent knows exactly what operation this is. It does not, however, differentiate itself from nearby siblings such as gmail_messages_get or gmail_threads_list, which it never mentions.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. At best the phrase 'matching a query' weakly implies bulk retrieval rather than fetching a single known message, but the agent must infer that contrast with gmail_messages_get on its own.

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