Skip to main content
Glama
Sign In
mcp-hey

mcp-hey

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hey_list_emails

Read-only

List emails from a Hey.com folder or view (imbox, feed, sent, etc.) with pagination; set force_refresh to bypass cached results.

Instructions

List emails in a Hey.com folder/view. Returns cached results unless force_refresh=true. Each email includes id, topicId, postingId, entryId, from, subject, date, and unread status. For folder=sent, from is always "Me" and the recipient (unverified against a live Sent page) is under to/toEmail instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder": "<folder>"
    },
    "name": "hey_list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination, 1-1000 (default: 1)
limitNoMaximum number of emails to return, 1-100 (default: 25)
folderYesThe folder/view to list emails from: imbox (important), feed (newsletters), paper_trail (receipts), trash, spam, drafts, or sent (emails you sent)
force_refreshNoBypass cache and fetch fresh data (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • changedInput schema / properties / folder / description
      Previous value: -"The folder/view to list emails from: imbox (important), feed (newsletters), paper_trail (receipts), trash, spam, or drafts"New value: +"The folder/view to list emails from: imbox (important), feed (newsletters), paper_trail (receipts), trash, spam, drafts, or sent (emails you sent)"
    • changedInput schema / properties / folder / enum
      Previous value: -[
-  "imbox",
-  "feed",
-  "paper_trail",
-  "trash",
-  "spam",
-  "drafts"
-]New value: +[
+  "imbox",
+  "feed",
+  "paper_trail",
+  "trash",
+  "spam",
+  "drafts",
+  "sent"
+]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of emails to return (default: 25)"New value: +"Maximum number of emails to return, 1-100 (default: 25)"
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination (default: 1)"New value: +"Page number for pagination, 1-1000 (default: 1)"
  2. Addedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond them: results are cached unless force_refresh=true, and it candidly flags that the sent-folder recipient field is unverified against a live Sent page — a real reliability caveat.

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?

Three front-loaded sentences: purpose, caching behavior, then returned fields. Each carries distinct information with no filler, though the return-field enumeration is somewhat list-like and could be trimmed.

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?

With no output schema, the description correctly compensates by enumerating the returned fields (id, topicId, postingId, entryId, from, subject, date, unread). Caching semantics and the sent-folder edge case round it out; only pagination/interaction with page and limit is left entirely to the schema.

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 coverage is 100%, so parameter definitions are already well documented (baseline 3). The description goes further by explaining force_refresh's cache-bypass effect in context and by describing the sent-folder quirk where from is always "Me" and the recipient moves to to/toEmail, which is nowhere in the schema.

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?

States a specific verb and resource ("List emails in a Hey.com folder/view") and scopes it to the folder/view axis, which distinguishes it from siblings like hey_list_label_emails and hey_list_collection_emails. It does not name those siblings explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the folder/view framing, and the force_refresh sentence signals when a cache bypass is warranted. However, it never says when to prefer this over hey_search or the label/collection listing tools, so the agent must infer the selection rule.

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

Deploy Server

Other Tools