Skip to main content
Glama
rishipradeep-think41

Google Workspace MCP Server

list_emails

Extract and display recent emails from a Gmail inbox using a specific search query, with options to limit the number of results.

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

  • The primary handler function for executing the 'list_emails' tool. It retrieves recent emails from the Gmail inbox, extracts headers and body content, and formats the response as JSON.
    private async handleListEmails(args: any) {
      try {
        const maxResults = args?.maxResults || 10;
        const query = args?.query || "";
        const getEmailBody = (payload: any): string => {
          if (!payload) return "";
    
          if (payload.body && payload.body.data) {
            return Buffer.from(payload.body.data, "base64").toString("utf-8");
          }
    
          if (payload.parts && payload.parts.length > 0) {
            for (const part of payload.parts) {
              if (part.mimeType === "text/plain") {
                return Buffer.from(part.body.data, "base64").toString("utf-8");
              }
            }
          }
    
          return "(No body content)";
        };
    
        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 || "";
            const body = getEmailBody(detail.data.payload);
    
            return {
              id: msg.id,
              subject,
              from,
              date,
              body,
            };
          })
        );
    
        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,
        };
      }
    }
  • Input schema definition for the 'list_emails' tool, specifying optional parameters for maxResults and query.
    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:63-79 (registration)
    Registration of the 'list_emails' tool in the ListToolsRequestSchema handler, including 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:274-275 (registration)
    Dispatch case in the CallToolRequestSchema switch statement that routes calls to the 'list_emails' handler.
    case "list_emails":
      return await this.handleListEmails(request.params.arguments);
  • Inner helper function used by handleListEmails to extract plain text body from Gmail message payloads, handling both simple and multipart messages.
    const getEmailBody = (payload: any): string => {
      if (!payload) return "";
    
      if (payload.body && payload.body.data) {
        return Buffer.from(payload.body.data, "base64").toString("utf-8");
      }
    
      if (payload.parts && payload.parts.length > 0) {
        for (const part of payload.parts) {
          if (part.mimeType === "text/plain") {
            return Buffer.from(part.body.data, "base64").toString("utf-8");
          }
        }
      }
    
      return "(No body content)";
    };
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 states the tool lists emails but doesn't describe what 'recent' means (e.g., time frame), whether it requires authentication, how results are ordered, or any rate limits. This leaves significant gaps in understanding 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's front-loaded and wastes no space, making it easy for an agent 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 for a tool with parameters and behavioral implications. It doesn't explain what 'recent' entails, the format of returned emails, or error conditions, leaving the agent with insufficient context for reliable use.

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 description coverage is 100%, with clear documentation for both parameters ('maxResults' and 'query'). The description doesn't add any parameter-specific details beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_emails' or 'modify_email', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'search_emails' or 'modify_email'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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/rishipradeep-think41/gsuite-mcp'

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