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);
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 mentions 'recent emails' but doesn't specify what 'recent' means (e.g., time frame, ordering), whether it's read-only or has side effects, or any rate limits or authentication needs. This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'recent' entails, the return format (e.g., list structure, fields), or how it differs from sibling tools like 'search_emails'. For a tool with 2 parameters and no structured behavioral hints, more context is needed.

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 both parameters ('maxResults' and 'query') with their types and default values. The description adds no additional parameter semantics beyond what the schema provides, meeting the baseline for high coverage.

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 action ('List') and resource ('recent emails from Gmail inbox'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'search_emails' or 'modify_email' beyond the basic verb, missing explicit distinction.

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 'search_emails' or 'modify_email'. The description implies a default listing of recent emails but offers no context on prerequisites, exclusions, or specific use cases.

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

Related 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/erickva/google-workspace-mcp-server-no-calendar-deletetion'

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