MCP Tool
inboxes_write
Manage inboxes and deposit or consume their events. Actions: `create` (requires `name`) returns the inbox including the ingest URL to POST to; `ingest` deposits an event (`id` + `body`) and needs only the inbox ID — no auth required, even for org-owned inboxes, since the ID is the capability; events expire after a TTL (the inbox default, or a per-event `ttl_seconds` override) and are then invisible to every read; `ack_event` (`id` + `event_id`) removes one event once you've processed it — list, process, then ack each event to drain the queue; `clear_events` removes all events for an inbox (`id`); `update`/`delete` act on an inbox (`id`).
Input schema
api_keystringOptional API key for authentication.action"create" | "update" | "delete" | "ingest" | "ack_event" | "clear_events"requiredThe operation to perform.idstringInbox ID (required for everything except create).event_idstringEvent ID (required for ack_event).namestringInbox name (required for create).descriptionstring | nullInbox description (null to clear).default_ttl_secondsintegerDefault TTL in seconds for events that don't set their own (60–2592000; default 86400).max_eventsinteger | nullMax pending events to retain (default 1000; null to reset).bodystringingest only: the event payload (any format, up to 1MB). May be omitted for an empty body.content_typestringingest only: MIME type of `body` (e.g. application/json). JSON bodies are also parsed and returned as parsed_body.ttl_secondsintegeringest only: per-event TTL override in seconds (60–2592000); defaults to the inbox's default_ttl_seconds.sourcestringingest only: optional producer label for the event.Example call
tools/call params
{
"name": "inboxes_write",
"arguments": {
"api_key": "agt_…",
"action": "create"
}
}