Skip to main content
Glama

Add Automation Queue

addAutomationQueue

Add a queue to an automation on a team that is on the Automations workspace, with or without revisions — membership is not versioned. The queue must not already belong to another automation; on a team that changes its automations by revision it cannot be moved between them at all, because the revisions binding it are immutable. Adding a queue that is already a member succeeds unchanged. A queue left behind by a deleted automation that ran as the team cannot join one that runs as its members (409 team_to_personal_move), and neither can a queue that an agent in an automation running as the team sends cases to (409 team_to_personal_queue).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "automation_id": "<automation_id>",
      "case_queue_id": "<case_queue_id>"
    },
    "name": "addAutomationQueue"
  }
}

Input Schema

NameRequiredDescriptionDefault
automation_idYesAutomation ID
case_queue_idYesQueue ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only supply the coarse safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds substantial behavior beyond that: membership is unversioned, revision bindings are immutable so a queue cannot be moved between revisions, and two distinct 409 error codes are named with their triggers. The only wrinkle is that "adding a queue that is already a member succeeds unchanged" describes no-op repeat behavior while idempotentHint is false — a mild tension rather than a direct contradiction, since adding new queues does mutate state.

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?

Nearly every clause carries operational content — workspace scoping, ownership constraint, revision immutability, idempotent re-add, and two error codes — with the core action front-loaded in the first clause. The writing is dense and clause-chained with heavy jargon, which costs readability, but there is little outright filler.

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 two-parameter mutation with no output schema, the description covers the constraints an agent needs to avoid predictable failures: workspace/team eligibility, ownership conflicts, revision immutability, and the two 409 cases. Missing pieces are minor — required permissions and whether a response body is returned are not mentioned.

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 coverage is 100% and both UUID parameters are fully constrained, so the schema carries the semantics and baseline 3 applies. The description adds contextual meaning to case_queue_id (membership, revision binding, cross-automation ownership) but says nothing about automation_id beyond the obvious, and offers no format or lookup guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause gives a specific verb and resource ("Add a queue to an automation") and scopes it to teams on the Automations workspace, which cleanly separates it from addAutomationAgent and from the inverse removeAutomationQueue. It stops short of explicitly naming those siblings as alternatives, so it is clear but not maximally differentiating.

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?

The description defines concrete preconditions and exclusions: the queue must not already belong to another automation, the team must be revision-based or not, and specific 409 conditions (team_to_personal_move, team_to_personal_queue) block the call. That is strong when-to-use/when-it-fails context, though it never explicitly routes the agent to a sibling (e.g. removeAutomationQueue or addAutomationAgent) for adjacent tasks.

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.

Resources