UiPath MCP Server

uipath_get_queue_stats

Retrieve queue statistics including item counts by status and success rate. Specify queue name and optional folder ID.

Instructions

Get statistics for a specific queue including item counts by status and success rate.

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

Input Schema

Name	Required	Description	Default
`folderId`	No	Folder ID where the queue exists
`queueName`	Yes	Name of the queue

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry the burden. It discloses the read-only nature via 'Get' and specifies output components, but does not mention prerequisites, error behavior, or any side effects.

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?

One sentence with no waste, directly front-loaded with the action and resource.

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?

For a simple get-stats tool, the description covers the main purpose and output highlights. It could be more explicit about the return shape, but given the schema covers parameters, it's sufficiently complete. No output schema means some return details would help, but the core is clear.

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 already documents both parameters thoroughly (100% coverage), and the description does not add extra meaning about how to use folderId or queueName beyond what's in the schema. Baseline 3 applies.

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 retrieves statistics for a named queue, specifying the nature of the stats (item counts by status, success rate). This differentiates it from sibling tools like get_queue_items which list individual items.

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

Usage Guidelines3/5

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

The description implies this is for aggregate queue statistics but does not explicitly state when to use it over alternatives like get_queue_items or get_job_stats. No when-not guidance is provided.

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