Skip to main content
Glama
stan13

ripper-mcp

by stan13

find_emails

Search and filter synced emails by keyword, folder, contact, unread or starred status, and date range. Returns matching emails with sender, subject, date, and snippet.

Instructions

Search or list the user's synced email. Pass a query to full-text search subject + body across the whole mailbox, and/or filter by folder, contactId (email from/to that contact), unreadOnly, starredOnly, or a date window (dateFrom/dateTo). Returns matching emails with their ids, sender, subject, date, folder, read/starred flags, and a snippet. This is the tool for 'did X email me', 'what's unread in my inbox', 'show me emails from this client', or 'find that email about the inspection'. Get an emailId here before get_email / update_email / delete_email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 15, max 50).
queryNoKeyword to match in subject or body. Optional when filtering by folder/contact/flags/date.
dateToNoISO 8601 date — only emails on or before this.
folderNoRestrict to one folder (inbox, sent, archive, trash, draft).
dateFromNoISO 8601 date — only emails on or after this.
contactIdNoOnly emails linked to this contact (from find_contacts).
unreadOnlyNoOnly unread emails.
starredOnlyNoOnly starred emails.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the full-text search behavior, combinable filters, and return fields. No destructive behavior is implied, which is appropriate for a search tool.

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 slightly long but front-loaded with purpose. Each sentence adds value, though minor redundancy exists ('Search or list' vs later 'full-text search'). Overall well-structured.

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

Completeness4/5

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

For a search tool with 8 parameters and no output schema, the description explains all filters, return fields, and provides usage examples. It is complete enough for an agent to use correctly.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds context: explains query is full-text search, filters can be combined, and lists return fields. It also clarifies the contactId parameter's usage.

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 the tool searches or lists synced emails with multiple filters. It distinguishes from sibling tools like get_email, update_email, delete_email, send_email by mentioning this is a prerequisite for those actions.

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?

The description includes explicit usage examples ('did X email me', 'what's unread in my inbox') and explains that get_email, update_email, delete_email require an emailId from this tool. It doesn't explicitly state when not to use, but the guidance is clear.

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/stan13/ripper-mcp'

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