UiPath MCP Server

list_queue_items

Retrieve queue items from UiPath Orchestrator, optionally filtered by queue name and status.

Instructions

List queue items, optionally filtered by queue name and status.

Args: queue_name: Optional queue name to filter by. status: Optional status filter (e.g. New, InProgress, Successful, Failed). top: Optional maximum number of items to return.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_queue_items"
  }
}

Input Schema

Name	Required	Description	Default
`queue_name`	No
`status`	No
`top`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 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 carries full burden but only states the action and optional filters. No information on side effects, authorization requirements, rate limits, pagination, or default behavior is provided.

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 extremely concise, with a single clear purpose sentence followed by a focused list of parameter explanations. Every word adds value without redundancy.

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

Completeness3/5

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

The description covers purpose and parameter semantics but omits return format, ordering, pagination limits, and default top value. Given no output schema, these gaps reduce completeness for a list operation.

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?

Despite 0% schema coverage, the description explicitly explains each parameter's purpose (e.g., 'Optional queue name to filter by'), adding semantic value beyond the schema's type and default 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 tool lists queue items and mentions optional filtering by name and status. The verb 'list' and resource 'queue items' are specific, and the tool is distinct from siblings with different resource names.

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 guidance on when to use this tool versus alternatives like list_jobs or list_assets. No context about prerequisites or exclusions is given, leaving the agent without usage direction.

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

Deploy Server