Skip to main content
Glama

Acknowledge or delete many inbox messages

inbox_bulk
DestructiveIdempotent

Webhook inbox pro: acknowledge (mark read) or delete many messages of an upgraded inbox at once; for one message on any inbox, inbox_ack or inbox_delete. ack takes ids or through and keeps them; delete takes through (that message and every older one, for good). Needs an active pro plan on that inbox (its own item: buy it after your human says yes), else 403 inbox_pro_required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "ack",
      "through": 42,
      "instance_id": "inb_exampleexampleexample2"
    },
    "name": "inbox_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoack only: these message ids.
actionYesack: mark read; delete: delete.
throughNoA message id: it and every older one.
instance_idYesThe inbox (inb_...).
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / through / description
      Previous value: -"A message id."New value: +"A message id: it and every older one."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "action": "ack",
      +    "instance_id": "inb_exampleexampleexample2",
      +    "through": 42
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real context: delete removes 'that message and every older one, for good' (scope of destruction plus irreversibility), ack merely marks read and keeps messages, and a pro plan is required or you get 403 inbox_pro_required. It does not explain what happens on partial failure or whether ack via 'through' also marks older messages read.

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?

One dense paragraph, front-loaded with the bulk ack/delete purpose before the sibling routing and prerequisites. Phrasing is compressed to the point of being slightly telegraphic ('Webhook inbox pro:', 'for good'), but nearly every clause carries decision-relevant information.

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?

For a destructive, plan-gated mutation tool with no output schema, the description covers purpose, alternatives, prerequisite, error code, and per-action parameter applicability. Remaining gaps are minor: whether combining ids with delete is an error, and whether ack via 'through' also affects older messages.

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 action-parameter binding the schema only partly encodes: 'ack takes ids or through and keeps them; delete takes through.' That tells the agent which parameter is valid for which action, beyond the terse schema hints.

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 (acknowledge/mark read, delete) on a specific resource (many messages of an upgraded/pro inbox) and scopes it as bulk. It explicitly contrasts with the single-message siblings inbox_ack and inbox_delete, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: bulk here, one message on any inbox goes to inbox_ack or inbox_delete. It also names a hard prerequisite (active pro plan on that inbox) and points at the buy flow and the 403 inbox_pro_required failure, which is exactly the guidance an agent needs before calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.