Skip to main content
Glama

Cooper Email

by com.cooperemail
OverviewDiscussionsAdmin

Create inboxes in a batch

cooper_create_inboxes
Destructive

Use this when the signed-in account needs several email addresses at once, or addresses that should disappear after a deadline (one inbox per signup, trial, or job). Requires auth. Inputs: count (required; how many inboxes, capped per plan), prefix (optional; addresses become prefix-@cooperemail.com, or box@cooperemail.com when omitted), labels (optional strings; filter later with GET /api/v1/inboxes?label=), metadata (optional object stored on every inbox; at most 256 keys, keys at most 256 characters, values string number or boolean, serialized at most 16 KB), ttl_hours (optional hours until expiry) or expires_at (optional ISO-8601 timestamp). Pass at most one of ttl_hours and expires_at. Returns {object:"list", data:[{id, username, email, display_name, created_at, require_sender_auth, labels, expires_at, status, paused_at, metadata, client_id}]}. Temporary inboxes count toward the plan inbox limit until they expire. The daily cron deletes expired inboxes and they then stop counting. Fails with 400 batch_count_exceeded when count is above the per-plan cap, 400 invalid_metadata, or 402 with upgrade_url when the plan inbox limit would be exceeded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesHow many inboxes to create. Capped per plan; each one counts toward the plan inbox limit.
labelsNoOptional labels stored on every inbox in the batch.
prefixNoOptional local-part prefix. Addresses are prefix-<random>@cooperemail.com.
metadataNoOptional caller data stored on every inbox in the batch. At most 256 keys, each key at most 256 characters, values string number or boolean, serialized at most 16 KB. Otherwise 400 invalid_metadata.
ttl_hoursNoOptional lifetime in hours. Omit both ttl_hours and expires_at for permanent inboxes.
expires_atNoOptional ISO-8601 expiry. Do not send this together with ttl_hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / metadata
      Added value: +{
+  "description": "Optional caller data stored on every inbox in the batch. At most 256 keys, each key at most 256 characters, values string number or boolean, serialized at most 16 KB. Otherwise 400 invalid_metadata.",
+  "type": "object"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations (which already flag destructive/write/open-world): temporary inboxes count toward the plan limit until the cron deletes them, the daily cron behavior, auth requirement, and specific error surfaces (400 batch_count_exceeded, 400 invalid_metadata, 402 with upgrade_url). This tells the agent exactly what side effects and failure modes to expect.

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?

Front-loaded with the usage condition and auth requirement, then parameters, then return shape and errors. It is dense and reads as a long block, but essentially every sentence carries operational information an agent needs.

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?

With no output schema, the description supplies the return shape ({object, data:[...]}) and the field list, plus plan-limit semantics and error codes. For a mutating batch tool with nested metadata constraints, this is complete enough to invoke 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 coverage is 100%, so the baseline is 3, but the description adds real value: the fallback address pattern box<random>@cooperemail.com when prefix is omitted, and the cross-field constraint to pass at most one of ttl_hours and expires_at. These are not obvious from the schema alone.

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 and resource with batch scope ('several email addresses at once'), which cleanly distinguishes it from the singular sibling cooper_create_inbox. The use-case framing (one inbox per signup, trial, or job) makes the tool's intent immediately legible without opening the schema.

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?

Gives a clear when-to-use condition: when multiple addresses are needed at once or when addresses should expire after a deadline. It does not explicitly name cooper_create_inbox as the alternative for single-inbox creation, nor state when-not to use it, so it falls short of a 5.

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

All Cooper Email 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