Skip to main content
Glama

Coline

List mail

list_mail_threads
Read-onlyIdempotent

Lists mail threads for inbox triage: what needs a reply, unread, starred, important or sent mail, newest first. Read one with read_mail_thread.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_mail_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonextCursor from the previous page, with the same filters.
filterNoinbox
accountIdNoOne account from list_mailboxes; default: all of them.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
threadsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond them, the newest-first ordering, but says nothing about pagination behavior or result volume even though the schema exposes a cursor and a 50-item cap.

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

Conciseness5/5

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

Two short sentences with the triage framing and the filter list front-loaded and the read-more pointer last. There is no redundant wording, and every clause carries information.

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?

With annotations covering safety and an output schema covering return values, the description only needs to convey purpose, filters and follow-up, all of which it does. The one gap is that paging through results with cursor is never hinted at in the prose, which matters for a list tool capped at 50 per call.

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 60% and the description names the filter modes (needs_reply, unread, starred, important, sent), which restates the enum values rather than adding meaning. The accountId, cursor and limit parameters get no explanation in the description, though cursor and accountId are documented in the schema itself, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list mail threads) plus the triage scope and the filter categories it covers, and says results come newest first. That is enough detail for an agent to distinguish it from search_mail or read_mail_thread without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"for inbox triage" gives a clear context for use and "Read one with read_mail_thread" explicitly routes the agent to the follow-up tool. It does not, however, say when to prefer search_mail over this listing, so the exclusion side of the guidance is missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources