Skip to main content
Glama

List, redrive or purge dead letters

queue_dead
Destructive

A queue's dead letters (messages claimed max_attempts times without an ack): list them (oldest first, each with body, attempts and last_error; page with after), redrive them back to the queue as new, attempts 0 (ids from list, or all: true), or purge them for good.

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": {
      "limit": 20,
      "queue": "jobs",
      "action": "list",
      "instance_id": "que_exampleexampleexample2"
    },
    "name": "queue_dead"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoredrive: every dead letter.
idsNoredrive: message ids (qms_...) from list.
afterNolist: next_after of the previous page.
limitNolist: how many (default 20).
queueYesQueue name: 1 to 64 characters from a-z 0-9 . _ -.
actionYeslist, redrive (back to the queue) or purge (delete).
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. Changed1 schema field changed
    • changedInput schema / properties / ids / description
      Previous value: -"redrive: these messages."New value: +"redrive: message ids (qms_...) from list."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "action": "list",
      +    "instance_id": "que_exampleexampleexample2",
      +    "limit": 20,
      +    "queue": "jobs"
      +  }
      +]
    • 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
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond them: list ordering (oldest first), the exact fields returned (body, attempts, last_error), pagination via after, the attempts-reset semantics on redrive, and the permanence of purge ('for good'). That is real behavioral disclosure, not restatement.

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 sentence with the definition front-loaded and zero filler, which is efficient. The nested parentheticals carrying the per-action detail make it slightly harder to parse at a glance than a short enumerated structure would be.

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 an 8-parameter, multi-action mutation tool with no output schema, the description covers the definition, per-action effects, list return fields, and pagination. It omits auth/prerequisite context (passport_token) and what happens to dead-letter records after redrive or to in-flight state during purge.

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 is 3, but the description adds relational meaning the schema does not: ids must come from a prior list call, all:true is the redrive-everything alternative to ids, and after is the next_after cursor from the previous page. It does not clarify that limit applies only to list beyond the schema's own text.

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?

The description names the specific resource (a queue's dead letters), defines it operationally (messages claimed max_attempts times without an ack), and enumerates all three modes (list, redrive, purge). An agent can distinguish this from queue_ack, queue_nack, and queue_claim 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?

It clearly defines what each action does and the condition that distinguishes redrive (back to the queue as new, attempts 0) from purge (permanent). It stops short of an explicit 'use X instead when' or a warning about when not to purge, so it sits just below the top band.

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.