Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List email threads

google_gmail_threads_list

List Gmail conversation threads newest first and filter them with an optional search query to find relevant email discussions quickly.

Instructions

List conversation threads, newest first, with an optional Gmail search query.

Input Schema

NameRequiredDescriptionDefault
queryNoGmail search query (e.g. from:bob, newer_than:2d).
accountNoAccount nickname to use.
pageTokenNoPage token from a previous result's nextPageToken.
maxResultsNoMax threads (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.95
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Page token from a previous result's nextPageToken.",
+  "type": "string"
+}
  2. Addedv0.1.60

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose two useful behaviors the schema does not: results are ordered newest-first and the query filter is optional, which implies an unfiltered full-listing mode. It omits pagination mechanics beyond the pageToken field and whether results are thread summaries, IDs, or full messages.

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 12-word sentence with no filler, front-loading the resource and its ordering. It is efficient but so terse that useful routing information was cut.

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?

Adequate for a simple read-only list call with fully documented params, but with no output schema the description should say what a returned item looks like (thread ID, snippet, message count) and how it differs from google_gmail_list. Those gaps matter for an agent choosing among ~10 Gmail listing siblings.

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 all four parameters (query, account, pageToken, maxResults) are already documented with defaults and limits. The description only echoes that query is optional; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ("List conversation threads") plus ordering ("newest first"), which is clear on its own. It never contrasts itself with the closely-related siblings google_gmail_list (messages) or google_gmail_threads_get (single thread), so the message-vs-thread distinction is left implicit.

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?

"with an optional Gmail search query" hints at filtering but gives no guidance on when to pick this over google_gmail_list or google_gmail_threads_get, and no preconditions (account selection, auth). Usage must be inferred entirely from the name.

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

Deploy Server

Other Tools