Skip to main content
Glama
erickva

Google Calendar - No deletion

by erickva

list_emails

Retrieve recent emails from Gmail inbox using a search query and specify the maximum number of results to filter and organize your inbox efficiently.

Instructions

List recent emails from Gmail inbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of emails to return (default: 10)
queryNoSearch query to filter emails

Implementation Reference

  • Implements the core logic for listing recent emails from the Gmail inbox. Fetches message list, retrieves details for each, extracts subject, from, and date headers, and returns as JSON-formatted text content.
    private async handleListEmails(args: any) {
      try {
        const maxResults = args?.maxResults || 10;
        const query = args?.query || '';
    
        const response = await this.gmail.users.messages.list({
          userId: 'me',
          maxResults,
          q: query,
        });
    
        const messages = response.data.messages || [];
        const emailDetails = await Promise.all(
          messages.map(async (msg) => {
            const detail = await this.gmail.users.messages.get({
              userId: 'me',
              id: msg.id!,
            });
            
            const headers = detail.data.payload?.headers;
            const subject = headers?.find((h) => h.name === 'Subject')?.value || '';
            const from = headers?.find((h) => h.name === 'From')?.value || '';
            const date = headers?.find((h) => h.name === 'Date')?.value || '';
    
            return {
              id: msg.id,
              subject,
              from,
              date,
            };
          })
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(emailDetails, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching emails: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Defines the input schema for the list_emails tool, specifying optional maxResults (number) and query (string) parameters.
    inputSchema: {
      type: 'object',
      properties: {
        maxResults: {
          type: 'number',
          description: 'Maximum number of emails to return (default: 10)',
        },
        query: {
          type: 'string',
          description: 'Search query to filter emails',
        },
      },
    },
  • src/index.ts:62-78 (registration)
    Registers the list_emails tool in the ListTools response, providing name, description, and input schema.
    {
      name: 'list_emails',
      description: 'List recent emails from Gmail inbox',
      inputSchema: {
        type: 'object',
        properties: {
          maxResults: {
            type: 'number',
            description: 'Maximum number of emails to return (default: 10)',
          },
          query: {
            type: 'string',
            description: 'Search query to filter emails',
          },
        },
      },
    },
  • src/index.ts:230-231 (registration)
    Registers the dispatch case for list_emails in the CallToolRequestSchema handler switch statement.
    case 'list_emails':
      return await this.handleListEmails(request.params.arguments);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'list recent emails', omitting crucial details such as required authentication, rate limits, output format (e.g., headers vs full content), and potential side effects.

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 a single concise sentence with no wasted words. However, it omits important details that could be included without much expansion, slightly reducing its efficiency.

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?

Given the sibling tools (especially 'search_emails'), the description fails to clarify when to use this tool versus searching. It also lacks return value details, pagination, and recency definition, making it incomplete for a tool with no output schema.

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 coverage is 100% with both parameters described ('query' for filtering, 'maxResults' with default). The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 'List recent emails from Gmail inbox', specifying the verb and resource. However, the term 'recent' is vague, and there is no differentiation from the sibling tool 'search_emails' which likely supports similar queries.

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 usage for listing recent emails but does not provide explicit guidance on when to use this tool versus alternatives like 'search_emails' or 'modify_email'. No context on prerequisites or limitations.

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

Related Tools