uipath-orchestrator-mcp

add_queue_item

Enqueue a new item into a UiPath Orchestrator queue by providing folder, queue name, and data, with optional priority and reference.

Instructions

Add a new item to a queue.

Args: folder_name: The display name of the folder. queue_name: The name of the queue. specific_content: Key-value pairs of data to store with the queue item. priority: Item priority — 'Low', 'Normal', or 'High' (default 'Normal'). reference: Optional reference string for tracking purposes.

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>",
      "specific_content": "<specific_content>"
    },
    "name": "add_queue_item"
  }
}

Input Schema

Name	Required	Default
`priority`	No	Normal
`reference`	No
`queue_name`	Yes
`folder_name`	Yes
`specific_content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior1/5

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

With no annotations, the description must fully disclose behavior, but it only states the action and parameter meanings. It does not mention effects on the queue, idempotency, permissions, or response format, leaving a significant transparency gap.

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 a concise list of arguments with one-line explanations and no filler. The first sentence front-loads the core action, and every line adds necessary parameter information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks any mention of output or return value, which is important because no output schema exists. It also omits error handling, preconditions, and differentiation from sibling tools, making it incomplete for a 5-parameter tool with nested content.

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?

Even though the schema has 0% description coverage, the description provides meaningful parameter semantics: priority values ('Low', 'Normal', 'High') with default, specific_content described as key-value pairs, and reference marked optional. This adds real value beyond the schema's raw type definitions.

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 description clearly states the action ('Add a new item to a queue') with a specific verb and resource. It is self-explanatory, though it does not explicitly distinguish itself from sibling tool bulk_add_queue_items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as bulk_add_queue_items or get_queue_items. There is no mention of prerequisites, contexts, or exclusions.

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