uipath-orchestrator-mcp

bulk_add_queue_items

Add multiple items to a UiPath Orchestrator queue in a single API call, choosing between all-or-nothing commit or processing each item independently.

Instructions

Add multiple items to a queue in a single API call.

Args: folder_name: The display name of the folder. queue_name: The name of the queue. items: List of item objects. Each item may contain: - specific_content (dict, required) — the data payload - priority (str, optional) — 'Low', 'Normal', or 'High' - reference (str, optional) — tracking reference commit_type: 'AllOrNothing' (default) — rolls back everything if any item fails; 'ProcessAllIndependently' — commits each item individually.

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": {
      "folder_name": "<folder_name>",
      "queue_name": "<queue_name>",
      "items": "<items>"
    },
    "name": "bulk_add_queue_items"
  }
}

Input Schema

Name	Required	Default
`items`	Yes
`queue_name`	Yes
`commit_type`	No	AllOrNothing
`folder_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.5/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 behavioral burden. It discloses important mutation traits via commit_type: 'AllOrNothing' rolls back on failure, while 'ProcessAllIndependently' commits each item. This provides transparency around failure handling beyond the schema.

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 well-organized with an Args section that lists each parameter and its semantics. Every sentence contributes information—there is no fluff. The main purpose is front-loaded, and the format is easy to scan.

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 has 4 parameters, nested item structures, and no output schema, the description covers all inputs and key failure modes (commit_type). It could be more complete by mentioning return values or error conditions, but it is sufficient for correct invocation in most cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the schema offers no property descriptions. The description compensates fully by explaining folder_name, queue_name, items (including nested object structure with specific_content, priority values, reference), and commit_type options. This exceeds the schema's bare types and titles.

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 opens with 'Add multiple items to a queue in a single API call' which clearly states the verb, resource, and scope. This distinguishes it from the sibling tool 'add_queue_item' that handles single items.

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 phrase 'in a single API call' implies bulk usage, and the sibling context makes the alternative obvious. However, there is no explicit when-to-use vs. when-not-to-use guidance, just a clear context that it is for multiple items.

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