Skip to main content
Glama
CSOAI-ORG

Email Automation MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_emails

Search emails in a folder using queries by sender, subject, or keywords. Supports full-text search, unread/flagged filters, and returns structured results.

Instructions

Search emails in a folder. Supports these query formats:

  • Email address: searches FROM field

  • 'subject:keyword': searches subject

  • 'from:name': searches sender

  • 'to:name': searches recipient

  • 'unread' or 'unseen': unread messages only

  • 'flagged' or 'starred': flagged messages

  • Any other text: full-text search

Args: query: Search query folder: IMAP folder to search (default: INBOX) limit: Max results (default: 10, max: 25)

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results. Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
folderNoINBOX
limitNo
api_keyNo

Tool Definition Quality

A3.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It explicitly states read-only, stateless, idempotent behavior, authentication requirements, rate limits (free vs. pro), error handling, and data privacy. This provides comprehensive behavioral transparency.

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?

The description is structured with sections but is verbose and contains redundant information (Behavior and Behavioral Transparency sections overlap). The generic 'When to use' section could be removed. Concision is adequate but not optimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description should explain return structure. It covers error objects but not success output. It also doesn't mention how api_key is used for authentication. These gaps reduce completeness despite good coverage of query formats and behavior.

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 coverage is 0%, so the description must compensate. It details query, folder (with default), and limit (with default and max), but misses the api_key parameter entirely. Query format explanation is thorough, but omission of api_key reduces score.

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

Purpose5/5

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

The description clearly states 'Search emails in a folder' with specific and varied query formats, distinguishing it from sibling tools like create_draft, list_folders, read_inbox, and send_email.

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 'When to use' section is generic and unrelated to searching emails, and there is no guidance on when to use this tool versus alternatives like read_inbox or list_folders. The query format examples offer implicit usage context but no explicit differentiation.

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/CSOAI-ORG/email-automation-mcp'

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