mcp-hey

Overview Schema Source Related Servers Discussions Admin

hey_collection

Idempotent

Add or remove an email thread from a collection using collection IDs from hey_list_collections. Reverse by calling again with the opposite action.

Instructions

Add or remove an email thread from a collection. Returns {success, error?}. Reversible by calling again with the opposite action. Use hey_list_collections to discover collection IDs.

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": {
      "topic_id": "<topic_id>",
      "collection_id": "<collection_id>",
      "action": "<action>"
    },
    "name": "hey_collection"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Whether to add or remove the thread from the collection
`topic_id`	Yes	The topic/thread ID to add to or remove from the collection
`collection_id`	Yes	The collection ID (use hey_list_collections to see available collections)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.1May 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds real value beyond the annotations: the return shape ({success, error?}) and the fact that the operation is reversible by calling again with the opposite action. Annotations already cover the safety/freshness profile (destructiveHint=false, idempotentHint=true), so the description's contribution is the response contract and undo path.

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?

Three short sentences with zero filler; the core action is front-loaded, followed by return shape, then the discovery hint. Every sentence carries distinct information.

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 3-parameter mutation with no output schema, the description covers the operation, the return contract, reversibility, and the ID-discovery prerequisite. Combined with complete schema coverage and annotations, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so topic_id, collection_id, and the action enum are already fully documented in the schema. The description only repeats the hey_list_collections hint for collection_id and adds nothing new about parameter format or constraints, matching the baseline for fully covered schemas.

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?

States a specific verb pair (add/remove) and a specific resource (an email thread within a collection), which an agent can distinguish from siblings such as hey_list_collections or hey_list_collection_emails. No ambiguity about what the tool mutates.

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 routes the agent to hey_list_collections to discover valid collection IDs, which is the key prerequisite for calling this tool. It stops short of stating when not to use it (e.g., versus hey_set_status or label tools), so it falls just below the top band.

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