Skip to main content
Glama
erickva

Google Calendar - No deletion

by erickva

search_emails

Locate specific emails in Gmail using advanced search queries to filter by sender, attachments, or other criteria, optimizing email retrieval efficiency.

Instructions

Search emails with advanced query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of emails to return (default: 10)
queryYesGmail search query (e.g., "from:example@gmail.com has:attachment")

Implementation Reference

  • The main handler function for the 'search_emails' tool. It uses the Gmail API to list messages matching the provided query, fetches detailed headers (subject, from, date) for each, and returns them as JSON.
    private async handleSearchEmails(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,
        };
      }
    }
  • Input schema definition for the 'search_emails' tool, specifying required 'query' parameter and optional 'maxResults'.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Gmail search query (e.g., "from:example@gmail.com has:attachment")',
          required: true
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of emails to return (default: 10)',
        },
      },
      required: ['query']
    },
  • src/index.ts:79-97 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: 'search_emails',
      description: 'Search emails with advanced query',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Gmail search query (e.g., "from:example@gmail.com has:attachment")',
            required: true
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of emails to return (default: 10)',
          },
        },
        required: ['query']
      },
    },
  • src/index.ts:232-233 (registration)
    Dispatcher case in CallToolRequestSchema handler that routes 'search_emails' calls to the handleSearchEmails function.
    case 'search_emails':
      return await this.handleSearchEmails(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 'advanced query' but fails to detail key traits like whether this is a read-only operation, potential rate limits, authentication requirements, or what the output format entails. For a search tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a tool with two parameters, though it could be slightly more informative without sacrificing brevity. The structure is front-loaded but lacks elaboration.

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 tool's complexity (search functionality with two parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like safety, performance, or output format, leaving the agent with insufficient context for reliable use. This is inadequate for a search tool without structured support.

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'), including defaults and examples. The description adds no additional semantic meaning beyond the schema, such as explaining query syntax further or contextualizing parameter interactions. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 verb ('search') and resource ('emails'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'list_emails' or 'modify_email', which might offer overlapping functionality. The 'advanced query' modifier adds some specificity but remains somewhat vague about what makes it 'advanced'.

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 'list_emails' or 'modify_email'. It lacks context about prerequisites, such as authentication needs or when advanced queries are preferable to simpler listing. This omission leaves the agent without clear usage boundaries.

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