Skip to main content
Glama
Sign In

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), signature (optional {text, html?} stored on every inbox in the batch), 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, signature}]}. signature is {text, html} or null. 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

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.
signatureNoUse this when every inbox in the batch should carry the same signature. text is required (non-empty, at most 2000 characters). html is optional (at most 10000 characters).
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.

Output Schema

NameRequiredDescriptionDefault
dataNoItems on this page, in the order the tool description gives.
objectNoObject type name, such as list, message, or thread.
noticesNoUsage notices, such as [{type: limit_warning, resource, used, limit, upgrade_url}] at 80 percent of a plan limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / signature / properties / html / description
      Added value: +"Optional HTML version of the signature for HTML sends."
    • addedInput schema / properties / signature / properties / text / description
      Added value: +"Plain-text signature added to the end of each send. Required when signature is set."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The inboxes created in this batch.",
+  "properties": {
+    "data": {
+      "description": "Items on this page, in the order the tool description gives.",
+      "items": {
+        "properties": {
+          "client_id": {
+            "description": "Caller idempotency key stored with the object, or null."
+          },
+          "created_at": {
+            "description": "ISO-8601 time the object was created."
+          },
+          "display_name": {
+            "description": "From display name, or null."
+          },
+          "email": {
+            "description": "Full email address of the inbox."
+          },
+          "expires_at": {
+            "description": "ISO-8601 time the object expires, or null for no expiry."
+          },
+          "id": {
+            "description": "Inbox id (inb_…). Pass it as inbox_id to other tools."
+          },
+          "labels": {
+            "description": "Labels on the object."
+          },
+          "metadata": {
+            "description": "Caller key-value data stored on the object."
+          },
+          "paused_at": {
+            "description": "ISO-8601 time the inbox was paused, or null."
+          },
+          "require_sender_auth": {
+            "description": "When true, only mail that passes DMARC/DKIM can create an owner task."
+          },
+          "screening": {
+            "description": "Inbound screening mode: off, observe, or hold."
+          },
+          "send_mode": {
+            "description": "direct sends immediately. approval turns sends into drafts a verified owner approves."
+          },
+          "signature": {
+            "description": "Signature {text, html} added to sends, or null."
+          },
+          "status": {
+            "description": "active or paused."
+          },
+          "username": {
+            "description": "Local part of the address."
+          }
+        },
+        "type": "object"
+      }
+    },
+    "notices": {
+      "description": "Usage notices, such as [{type: limit_warning, resource, used, limit, upgrade_url}] at 80 percent of a plan limit."
+    },
+    "object": {
+      "description": "Object type name, such as list, message, or thread."
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "Use this when every inbox in the batch should carry the same signature. text is required (non-empty, at most 2000 characters). html is optional (at most 10000 characters).",
+  "properties": {
+    "html": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
  3. 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"
+}
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, and the description layers on substantive operational context: auth required, per-plan count caps, temporary inboxes counting against the plan limit until they expire, a daily cron deleting expired inboxes, and specific failure codes (400 batch_count_exceeded, 400 invalid_metadata, 402 with upgrade_url). That is exactly the quota and failure behavior an agent cannot get from the schema or hints.

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 when-to-use condition, then inputs, then return shape, then quota and error semantics — a sensible ordering in one dense paragraph. A few clauses restate schema text verbatim (the 256-key / 16 KB metadata limits, signature length rules), which is the main wasted space, and the paragraph is long enough that scanning is harder than a bulleted layout.

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 batch mutation tool with seven parameters, a nested signature object, annotations, and an output schema, the description covers scope, auth, param interactions, quota accounting, lifecycle (cron deletion), and error codes. Nothing an agent needs to call it correctly or interpret a failure is missing.

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 baseline would be 3, but the description adds real meaning: prefix yields prefix-<random>@cooperemail.com and falls back to box<random>@... when omitted, labels can be filtered later via GET /api/v1/inboxes?label=, and ttl_hours/expires_at are mutually exclusive ('pass at most one'). The mutual-exclusion rule is a genuine constraint the schema only states one-sidedly.

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 with explicit batch scope ('several email addresses at once'), which separates it from the singular cooper_create_inbox by capability rather than by name. It also names concrete use cases (one inbox per signup, trial, or job), so an agent knows what shape of task it fits, though it never explicitly cites the single-create sibling as the alternative.

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?

'Use this when the signed-in account needs several email addresses at once, or addresses that should disappear after a deadline' gives a clear triggering condition plus example scenarios. It also flags the auth requirement. It stops short of a when-not rule (e.g., 'for a single address use cooper_create_inbox'), so the routing decision is implied rather than spelled out.

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