Skip to main content
Glama

search_emails

Query and retrieve emails from specific accounts using Microsoft Graph API. Input search terms, account ID, and optional filters to streamline results.

Instructions

Search emails using the modern search API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
folderNo
limitNo
queryYes

Implementation Reference

  • The main handler function for the 'search_emails' tool. It performs email searches using either folder-specific traditional search or unified modern search via Microsoft Graph API, depending on whether a folder is specified.
    @mcp.tool
    def search_emails(
        query: str,
        account_id: str,
        limit: int = 50,
        folder: str | None = None,
    ) -> list[dict[str, Any]]:
        """Search emails using the modern search API."""
        if folder:
            # For folder-specific search, use the traditional endpoint
            folder_path = FOLDERS.get(folder.casefold(), folder)
            endpoint = f"/me/mailFolders/{folder_path}/messages"
    
            params = {
                "$search": f'"{query}"',
                "$top": min(limit, 100),
                "$select": "id,subject,from,toRecipients,receivedDateTime,hasAttachments,body,conversationId,isRead",
            }
    
            return list(
                graph.request_paginated(endpoint, account_id, params=params, limit=limit)
            )
    
        return list(graph.search_query(query, ["message"], account_id, limit))
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 using a 'modern search API' but doesn't explain what this entails—such as search capabilities, performance characteristics, authentication needs, rate limits, or return format. This leaves significant gaps for a search operation.

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 with no wasted words. It's 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 tool's complexity (search operation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address key aspects like search behavior, result format, or error handling, leaving the agent with insufficient context.

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

Parameters2/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 by explaining parameters. It adds no meaning beyond the schema, failing to clarify what 'account_id', 'folder', 'limit', or 'query' entail, such as query syntax or folder options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool searches emails using a modern search API, which provides a basic verb+resource combination. However, it doesn't specify what makes it 'modern' or how it differs from sibling tools like 'list_emails' or 'unified_search', leaving the purpose somewhat vague.

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 'list_emails' or 'unified_search'. The description merely states what the tool does without indicating appropriate contexts or exclusions.

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/elyxlz/microsoft-mcp'

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