Skip to main content
Glama

Create, change or delete a queue

queue_settings
DestructiveIdempotent

Create a queue or change its settings: lease, max_attempts before dead letter, max_messages (fields left out stay); returns the queue as queue_status shows it. Optional: queue_put makes a queue on first use, with a 60 s lease, 5 attempts and room for 10,000 messages. delete: true deletes the queue with all its messages, 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": {
      "queue": "jobs",
      "instance_id": "que_exampleexampleexample2",
      "max_attempts": 5,
      "visibility_timeout_seconds": 120
    },
    "name": "queue_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
queueYesQueue name: 1 to 64 characters from a-z 0-9 . _ -.
deleteNotrue: delete the queue and its messages.
instance_idYesUtility instance id from buy or list_utilities.
max_attemptsNoClaims before a message goes to the dead letters.
max_messagesNoSize limit of the queue.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
visibility_timeout_secondsNoDefault lease in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "que_exampleexampleexample2",
      +    "max_attempts": 5,
      +    "queue": "jobs",
      +    "visibility_timeout_seconds": 120
      +  }
      +]
    • 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. 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}$"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real context beyond them: partial-update semantics ('fields left out stay'), permanence of delete ('with all its messages, for good'), the return shape ('as queue_status shows it'), and the defaults queue_put applies (60 s lease, 5 attempts, 10,000 messages). It stops short of mentioning auth expectations (the passport_token path) or limits on settings changes.

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 primary action and then the optional and destructive branches in descending importance, with no filler. The semicolon-and-colon chaining is dense and slightly run-on, but every clause carries information an agent needs.

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 7-parameter, destructive, no-output-schema mutation tool, the description covers the return value, partial-update behavior, delete consequences, and implicit-creation defaults. The only meaningful omission is authentication guidance around passport_token, which the schema's own description largely covers.

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; the description earns an extra point by explaining update semantics that the schema does not convey — omitted fields are preserved rather than reset, and delete removes the queue together with its messages. It does not add format or unit detail beyond the schema, but the partial-update clarification is genuinely load-bearing.

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 set and resource: 'Create a queue or change its settings' plus the delete mode, and enumerates the mutable fields (lease, max_attempts, max_messages). It also distinguishes itself from queue_put by noting that queue_put only creates a queue implicitly on first use, so an agent can pick between them 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 Guidelines3/5

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

Usage is implied rather than stated: the queue_put sentence signals that this tool is the explicit way to create/configure a queue, and 'delete: true' marks the destructive branch. There is no explicit when-to-use/when-not-to-use guidance (e.g., preferring queue_put for one-off sends), leaving the routing 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.