uipath-orchestrator-mcp

retry_queue_item

Retry a failed or abandoned queue item by resetting its status to New, enabling robots to pick it up again. Requires item ID, row version, and folder.

Instructions

Retry a Failed or Abandoned queue item, resetting it to New so robots will pick it up again.

Only applicable to items with status Failed or Abandoned — retrying items in other states will return an API error. The row_version field is returned with each queue item from get_queue_items and is required for optimistic concurrency control.

Args: queue_item_id: The ID of the queue item to retry. row_version: The RowVersion value from the queue item (prevents stale retries). folder_name: The display name of the folder containing the item.

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": {
      "queue_item_id": "<queue_item_id>",
      "row_version": "<row_version>",
      "folder_name": "<folder_name>"
    },
    "name": "retry_queue_item"
  }
}

Input Schema

Name	Required	Description	Default
`folder_name`	Yes
`row_version`	Yes
`queue_item_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the state reset to New, the error condition for non-eligible states, and the optimistic concurrency control mechanism via row_version. This goes beyond basic mutation descriptions, though it does not mention return values or side effects beyond the state change.

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?

The description is concise and well-structured: a clear one-sentence purpose, a brief usage constraint paragraph, and a simple Args list. No superfluous content; every sentence earns its place.

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?

Given the tool's simplicity (3 required params, no output schema), the description covers all essential aspects: purpose, applicable states, error condition, concurrency, and parameter semantics. It does not explicitly describe the return value, but with no output schema, that is not strictly necessary. Minor gap could be mentioning any required permissions, but overall it is complete enough.

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?

The input schema has 0% description coverage, but the description's Args section adds meaning to all three parameters. It explains queue_item_id as the ID, row_version as the value from get_queue_items preventing stale retries, and folder_name as the display name. This compensates well for the schema's lack of descriptions.

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 clearly states the tool's function: 'Retry a Failed or Abandoned queue item, resetting it to New so robots will pick it up again.' This is a specific verb (retry), resource (queue item), and state change (resetting to New), distinguishing it from sibling tools like add_queue_item or delete_queue_item.

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 provides clear context on when to use the tool: only for items with status Failed or Abandoned, explicitly stating other states will return an API error. It also implies the need to first fetch items via get_queue_items to obtain row_version. However, it does not explicitly name alternative tools for other scenarios, so it falls just short of a 5.

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