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

Google Workspace (GWS) MCP Server

gmail_threads_list

Read-only

List Gmail threads matching a Gmail search query for a user, with optional result limits, to locate relevant email conversations.

Instructions

List Gmail threads 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_threads_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoGmail search query
userIdYesUser ID (use 'me')
maxResultsNoMax threads 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 the safety profile is covered structurally. The description adds nothing further — no note on pagination behavior, result ordering, empty-query behavior, or what identifying data each thread carries.

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 short sentence with the resource and filter front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than tight editing of rich content.

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?

The tool is simple (three params, no output schema), but the description never indicates what is returned (thread IDs vs. full threads) or how maxResults interacts with paging. For a list endpoint whose output shape is undocumented, that gap matters to an agent deciding whether to call this or fetch messages.

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 q, userId, and maxResults are each documented in the schema, including the useful "use 'me'" hint. The description only echoes the query concept and adds no syntax examples or default-value information beyond 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 uses a specific verb plus resource ("List Gmail threads") and adds the scoping condition "matching a query," so an agent knows exactly what the tool returns. It does not, however, distinguish itself from close siblings such as gmail_messages_list or gmail_threads_get.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives like gmail_messages_list for message-level results or gmail_threads_get for a single thread. The agent must infer the choice from the name alone.

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