Skip to main content
Glama
Sign In
Email MCP Server

Email MCP Server

by Rajath2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_recent_emails

Returns a list of the most recent emails from your inbox, showing subject and sender without the body. You can specify the maximum number to retrieve.

Instructions

List the most recent emails in the inbox (without bodies).

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": "list_recent_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of emails to return (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses that the tool returns only recent emails without bodies, implying a read-only, non-destructive operation. However, since no annotations are provided, it does not explicitly state its side-effect free nature, required authentication, or the exact sorting criteria. This is adequate but could be more explicit.

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?

The description is a single, concise sentence that front-loads the core purpose. Every word is meaningful, with no redundancy or filler.

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 does not specify what fields are returned in the email list (e.g., subject, sender, timestamp), nor does it mention any pagination or handling of large result sets. Given the lack of an output schema, the description should provide more detail on the response format to be fully complete.

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?

The schema already provides a description for the only parameter 'limit' (default 5). The tool description adds no additional semantic value beyond what the schema offers, so it meets the baseline of 3.

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 description clearly states the action ('List'), the resource ('most recent emails'), and the scope ('inbox'), while also specifying what is excluded ('without bodies'). This distinguishes it from sibling tools 'read_email' (which likely includes bodies) and 'summarize_email' (which would provide a summary).

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

Usage Guidelines3/5

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

The description implies that if bodies are needed, one should use 'read_email' instead, but it does not explicitly state when to use this tool versus its siblings. No direct guidance on prerequisites or alternatives is provided beyond the implication from the 'without bodies' qualifier.

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