Skip to main content
Glama

get_email

Retrieve full email details including body content, headers, and metadata by providing the email ID obtained from list_emails() or search_emails() results.

Instructions

    Get a specific email by ID.
    
    This tool retrieves the full details of a specific email, including
    the body content, headers, and other metadata.
    
    Prerequisites:
    - The user must be authenticated. Check auth://status resource first.
    - You need an email ID, which can be obtained from list_emails() or search_emails()
    
    Args:
        email_id (str): The ID of the email to retrieve. This ID comes from the
                        list_emails() or search_emails() results.
        
    Returns:
        Dict[str, Any]: The email details including:
            - id: Email ID
            - thread_id: Thread ID
            - subject: Email subject
            - from: Sender information
            - to: Recipient information
            - cc: CC recipients
            - date: Email date
            - body: Email body content
            - snippet: Short snippet of the email
            - labels: Email labels
            - email_link: Direct link to the email in Gmail web interface
            
    Example usage:
    1. First check authentication: access auth://status resource
    2. Get a list of emails: list_emails()
    3. Extract an email ID from the results
    4. Get the full email: get_email(email_id="...")
    5. Always include the email_link when discussing the email with the user
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
email_idYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: authentication requirements ('The user must be authenticated'), data source dependencies (email ID from other tools), and usage guidance ('Always include the email_link when discussing the email with the user'). However, it doesn't mention rate limits, error conditions, or performance characteristics.

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 well-structured with clear sections (purpose, prerequisites, args, returns, example usage) and front-loaded with the core purpose. However, the example usage section is somewhat verbose and could be more concise while maintaining clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description provides comprehensive context: clear purpose, usage guidelines, parameter semantics, detailed return value documentation, and practical examples. It addresses all necessary aspects for a read operation with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate fully. It provides rich semantic context for the single parameter: explains what email_id is, where it comes from (list_emails() or search_emails()), and its purpose. This adds significant value beyond the bare schema.

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 specific action ('retrieves the full details of a specific email') and resource ('email by ID'), distinguishing it from siblings like list_emails (which lists multiple emails) and search_emails (which searches with criteria). The verb 'retrieves' is precise and the scope is well-defined.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Get a specific email by ID') and provides clear prerequisites (authentication, obtaining email ID from list_emails() or search_emails()). It also distinguishes from alternatives by specifying this is for retrieving a single email by ID, not listing or searching multiple emails.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bastienchabal/gmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server