UiPath MCP Server

uipath_get_robot_logs

Fetch robot logs with optional filters to diagnose automation issues and monitor performance.

Instructions

Get robot logs with optional filters.

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_robot_logs"
  }
}

Input Schema

Name	Required	Description
`skip`	No	Number of items to skip (default 0)
`level`	No	Filter by log level
`limit`	No	Maximum items to return (default 100)
`jobKey`	No	Filter by job key
`endTime`	No	Filter by end time (ISO 8601)
`folderId`	No	Folder ID to filter robot logs
`startTime`	No	Filter by start time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.9/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 only says 'Get robot logs' without mentioning return format, permissions, side effects, or filter semantics. This adds minimal transparency beyond the schema.

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 single, efficiently front-loaded sentence that immediately identifies the verb and resource. No unnecessary words.

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?

Given the 7 optional parameters, no output schema, and no annotations, the description is too thin. It does not explain what robot logs contain, how filters combine, or pagination behavior, leaving the agent to rely solely on schema fields.

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 has 100% parameter description coverage, so the baseline is 3. The description's 'optional filters' summarizes that all parameters are optional but doesn't add meaning beyond what the schema already provides.

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 retrieves robot logs and supports optional filters. It distinguishes the resource (robot logs) from sibling tools like audit logs, though it doesn't explicitly contrast with alternatives.

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_audit_logs. The phrase 'with optional filters' hints at usage but offers no exclusions or decision criteria.

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