Skip to main content
Glama
Sign In
fastmcp-gsuite

fastmcp-gsuite

by tumf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

query_gmail_emails

Retrieve Gmail emails using search queries such as 'is:unread' or 'from:example@gmail.com'. Returns results sorted by newest first.

Instructions

Query Gmail emails based on an optional search query. Returns emails in reverse chronological order (newest first).

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": {
      "user_id": "<user_id>"
    },
    "name": "query_gmail_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe EMAIL of the Google account. Choose from:
queryNoGmail search query (e.g., 'is:unread', 'from:example@gmail.com')
max_resultsNoMaximum number of emails (1-500, default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the ordering (reverse chronological) but does not explicitly state that the tool is read-only (non-destructive) or mention any other behaviors like pagination or authentication requirements.

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 sentences, front-loaded with the primary action, and no wasted words. The structure efficiently conveys the essential purpose and ordering detail.

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?

The description is adequate for a simple query tool but lacks context on pagination, how to select the user_id (only partially described in schema), and does not mention that it returns metadata (no output schema). The absence of annotations leaves some gaps.

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 the schema already documents all parameters (user_id, query, max_results). The description adds no new parameter information beyond 'optional search query', achieving only the baseline 3.

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 clearly states the tool queries Gmail emails with an optional search query and specifies reverse chronological order. However, it does not differentiate from siblings like bulk_get_gmail_emails or get_email_details, which may also retrieve emails but by different criteria.

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?

No guidance is provided on when to use this tool versus alternatives such as bulk_get_gmail_emails or get_email_details. The context for choosing this tool is implied by the name but not explicit.

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