Skip to main content
Glama

search_emails

Search your macOS Mail inbox by keyword, sender, or date range to quickly locate specific messages.

Instructions

Search emails by keyword, sender, or date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:15-15 (registration)
    Tool definition and registration entry for 'search_emails' in the TOOLS array. The tool is registered with the description 'Search emails by keyword, sender, or date range'.
    ["search_emails", "Search emails by keyword, sender, or date range"],
  • Generic handler stub for all tools including 'search_emails'. This is a minimal MCP inspection stub that returns a placeholder message; the real implementation exists in a native binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
  • server.js:106-110 (registration)
    Registration loop that calls server.tool() for each tool including 'search_emails', registering it with an empty schema and a stub handler.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior1/5

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

Description claims search by keyword, sender, or date range, but input schema has zero parameters, making the tool unusable as described. No annotations exist to compensate. This is a critical contradiction between description and schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no waste, but overly brief given the tool's complexity and contradictory nature.

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?

Missing essential information: parameters are described but not defined, no output schema. Incomplete to enable correct usage.

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?

Although schema coverage is 100% with zero parameters, the description adds meaning by listing filter types. However, these filters do not exist in the schema, so the description is misleading. Baseline for zero params is 4, but mismatch reduces score.

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 tool searches emails and mentions common filters (keyword, sender, date range), distinguishing it from 'list_emails' which likely returns all emails. However, it does not explicitly differentiate from sibling 'outlook_search_emails'.

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 on when to use search vs. other email tools (e.g., list_emails, read_email). Lacks context for selection among siblings.

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

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/lanchuske/local-mcp-releases'

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