Skip to main content
Glama

radmail-mcp

by ai.radmail
OverviewDiscussionsAdmin

search

Find a specific message by sender, subject, or content. Results come back most-relevant + newest first, and every hit says where it matched (from / subject / body) and why. On this hosted sandbox it searches the built-in demo inbox; run the radmail-mcp package with RADMAIL_API_KEY set and the same tool searches your REAL ingested inbox read-only (with from / after / before filters) via the v1 search API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax hits to return (default 10).
queryYesWords to find, matched against from / subject / body. Every word must appear somewhere in a message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max hits to return (default 10, max 25)."New value: +"Max hits to return (default 10)."
    • changedInput schema / properties / query / description
      Previous value: -"What to find — a sender, a subject word, or content terms. ALL terms must match. E.g. 'acme delivery' or a sender name."New value: +"Words to find, matched against from / subject / body. Every word must appear somewhere in a message."
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max hits to return (default 10)."New value: +"Max hits to return (default 10, max 25)."
    • changedInput schema / properties / query / description
      Previous value: -"Words to find, matched against from / subject / body. Every word must appear somewhere in a message."New value: +"What to find — a sender, a subject word, or content terms. ALL terms must match. E.g. 'acme delivery' or a sender name."
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Despite no annotations, description discloses result ordering, match attribution, and read-only nature in real mode. Could mention if sandbox is also read-only, but overall strong behavioral context.

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?

Two sentences, efficient, front-loaded with core purpose, no redundant phrasing.

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

Completeness5/5

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

For a search tool with 2 params and no output schema, description covers purpose, usage contexts, result format, and ranking. No missing critical information.

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 100%, so baseline is 3. Description adds value by explaining result format (match location, relevance ranking) but does not add new parameter-specific details beyond schema.

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?

Clearly states it finds a message by sender, subject, or content, and describes result ranking and match highlighting. Distinguishes itself from sibling tools (e.g., draft_reply, triage_inbox) which are not search-related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes two usage contexts: sandbox (demo inbox) and real (with API key, read-only, with filters). Does not provide explicit 'when not to use' but context is clear and no conflicting sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All radmail-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources