UiPath MCP Server

uipath_get_queue_definitions

Retrieve all queue definitions from UiPath Orchestrator to view queue configurations and filter by folder ID.

Instructions

Get all queue definitions from UiPath Orchestrator. Returns list of queues with their configuration.

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": "uipath_get_queue_definitions"
  }
}

Input Schema

Name	Required	Description	Default
`folderId`	No	Folder ID to filter queue definitions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Without annotations, the description carries the burden of behavioral disclosure. It indicates a read-only operation ('Get' and 'Returns list') but does not mention pagination, filtering behavior beyond the optional folderId, or any constraints. It is transparent enough for a simple getter but lacks depth.

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 action and resource, and contains no redundant content. Every word earns its place, making it highly concise and well-structured.

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?

While the description states the return value as a list of queues with configuration, it lacks details about the structure of the returned objects, pagination, or how the optional folderId filter affects the results. Given there is no output schema, more specifics would help the agent understand what to expect.

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 single optional parameter 'folderId' is fully described in the schema, so the description does not need to add semantics. It adds no additional parameter information beyond what the schema already provides, meeting the baseline for full schema coverage.

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 gets all queue definitions from UiPath Orchestrator and returns their configuration, which distinguishes it from sibling tools like uipath_get_queue_items (which deals with items within queues). The verb 'Get' and resource 'queue definitions' are specific and unambiguous.

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 on when to use this tool versus alternatives such as uipath_get_queue_items or uipath_get_queue_stats, nor any scenarios or exclusions. The description simply states what it does without contextualizing when it should be chosen.

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