Skip to main content
Glama

Delete an inbox message

inbox_delete
DestructiveIdempotent

Delete one message of your webhook inbox for good; an unknown or already deleted message_id: 404 message_not_found. To keep it but mark it read, inbox_ack. Works after the plan ended too.

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": {
      "message_id": 42,
      "instance_id": "inb_exampleexampleexample2"
    },
    "name": "inbox_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe message's id from inbox_messages.
instance_idYesUtility instance id from buy or list_utilities.
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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "inb_exampleexampleexample2",
      +    "message_id": 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."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: deletion is permanent ('for good'), a repeat/unknown id yields 404 message_not_found, and the tool keeps working after the plan has ended. It doesn't mention the passport_token fallback path, which is the remaining behavioral gap.

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 compact clauses, front-loaded with the destructive action and permance, then the error behavior, then the alternative tool. Nothing is padded and no sentence could be dropped without losing routing or safety 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 three-parameter destructive tool with full schema coverage, an output schema absent, and complete annotations, the description covers the essentials: what is destroyed, what error to expect, what to use instead, and a non-obvious availability caveat. Only the credential fallback path is left unaddressed, which the schema partially handles.

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 all three parameters are documented in the schema and the baseline is 3. The description does clarify the meaning of an invalid message_id (404 message_not_found), which is a small addition over the schema, but it says nothing new about instance_id or passport_token.

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 ('Delete one message of your webhook inbox') with explicit scope ('one message') and 'for good' permanence. It also names the sibling it is not (inbox_ack), so an agent can separate the two without opening any schema.

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 a concrete routing rule: 'To keep it but mark it read, inbox_ack' names the alternative and the condition that selects it. It also sets expectations for the failure path (unknown or already deleted message_id returns 404 message_not_found) rather than leaving it to inference.

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.