Skip to main content
Glama
Sign In
Gmail MCP Server

Gmail MCP Server

by ampcome-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

gmail_get_stats

Retrieve Gmail account statistics including total messages, threads, and optionally unread count for quick overview of mailbox activity.

Instructions

Get Gmail account statistics.

Args: include_unread: Include unread message count

Returns: Dictionary with account statistics

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

Input Schema

NameRequiredDescriptionDefault
include_unreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication needs, or rate limits. It only states the return type as a dictionary.

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?

The description is very concise with two sentences, but it lacks depth. It front-loads the purpose but could be more informative without significant length increase.

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 description omits key details such as which specific statistics are returned, the format of the dictionary, and any prerequisites. This leaves the agent with incomplete information 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?

The description adds minimal value over the input schema; 'Include unread message count' is nearly identical to the schema title 'Include Unread'. No additional details on default behavior or impact on output are given.

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?

The name and description clearly state 'Get Gmail account statistics', which is a specific verb and resource. It distinguishes itself from sibling tools that deal with individual messages.

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 like gmail_list_messages or gmail_search_messages. The description merely states what it does without context.

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