UiPath MCP Server

uipath_add_queue_item

Add an item to a UiPath queue for automated processing by robots. Specify queue name, data, and optional priority or reference.

Instructions

Add a new item to a UiPath queue. The item will be processed by robots.

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": {
      "queueName": "<queueName>",
      "data": "<data>"
    },
    "name": "uipath_add_queue_item"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	The data/content for the queue item
`folderId`	No	Folder ID where the queue exists
`priority`	No	Item priority (default Normal)
`queueName`	Yes	Name of the queue to add item to
`reference`	No	Optional unique reference for tracking

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions that the item 'will be processed by robots', hinting at asynchronous behavior, but doesn't disclose details like whether the queue must exist, potential failure modes, or what the response contains. This is insufficient for a write operation.

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 two short sentences, front-loaded with the primary action and resource. Every word earns its place, with no unnecessary detail or repetition.

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?

Despite having 5 parameters including a nested object, no output schema, and no annotations, the description provides very little context. It doesn't explain what 'data' should contain, how priority/reference interact, or what happens after the call. This left the agent with significant gaps for a tool with such complexity.

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?

The schema descriptions cover 100% of parameters, so the baseline is 3. The tool description adds no additional parameter-specific meaning beyond the schema, but it doesn't need to since the schema already documents each parameter effectively.

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 explicitly states the action ('Add a new item') and the resource ('a UiPath queue'), and adds context that the item will be processed by robots. This clearly distinguishes it from sibling read-only tools like uipath_get_queue_items and uipath_get_queue_stats.

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?

The description provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It only states the general purpose, leaving the agent to infer usage from the tool name and context.

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