Skip to main content
Glama

gmail list threads

gmail_list_threads
Read-onlyIdempotent

List Gmail threads matching an optional query and cap the number of results to retrieve relevant email conversations for review, triage, or automation.

Instructions

List Gmail threads matching an optional query.

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_list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered by structured data. The description adds nothing beyond that: no mention of pagination, result ordering, how max_results is capped, or whether an empty query returns everything, which is the key behavioral question for a list tool.

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?

One short, front-loaded sentence with no filler. It is efficient rather than verbose; the problem is under-specification, not wordiness.

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?

An output schema exists, so return values need not be explained, but for a listing tool with an openWorld hint the description should clarify query semantics, default/cap behavior of max_results, and how threads differ from messages. None of that is present, leaving real gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, and it does not. It signals that 'query' is optional but gives no guidance on query syntax (e.g. Gmail search operators) and never mentions 'max_results' (default 10), leaving both parameters under-specified.

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 gives a specific verb and resource ('List Gmail threads') plus the filtering dimension ('matching an optional query'), so the agent knows this is a read/list operation over threads. It does not differentiate from the sibling gmail_search_messages, which an agent could reasonably confuse with this tool, so it stops short of a 5.

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 guidance at all: nothing says when to prefer this over gmail_search_messages, get_message, or list_labels, and no preconditions (auth/scope) are stated. The only hint is the word 'optional', which implies the tool works with or without a query.

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