UiPath MCP Server

uipath_get_audit_logs

Retrieve audit logs from UiPath Orchestrator to track user actions and timestamps for compliance and debugging.

Instructions

Get audit log entries from UiPath Orchestrator. Tracks who did what and when - useful for compliance and debugging.

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

Input Schema

Name	Required	Description
`skip`	No	Number of items to skip (default 0)
`limit`	No	Maximum items to return (default 50)
`action`	No	Filter by action type (e.g. 'Create', 'Update', 'Delete')
`endTime`	No	Filter by end time (ISO 8601)
`userName`	No	Filter by user name
`component`	No	Filter by component (e.g. 'Jobs', 'Queues', 'Robots')
`startTime`	No	Filter by start time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only operation with 'Get' and describes the log content as 'who did what and when,' but it does not disclose pagination behavior, required permissions, or error handling. Some transparency is present but not comprehensive.

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 with no redundant words. The purpose and value are stated directly and efficiently.

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 read-only tool with all parameters documented in the schema, the description adequately covers purpose and data nature ('tracks who did what and when'). It doesn't mention return format details, but the absence of an output schema is mitigated by the implied log entry fields. Missing notes on default pagination are covered by the schema's parameter descriptions.

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 input schema has 100% description coverage for all 7 parameters, so the schema does the heavy lifting. The description adds only high-level mapping ('who did what and when' roughly maps to userName/action/startTime/endTime) without providing additional meaning beyond the schema.

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 'Get audit log entries from UiPath Orchestrator' with a specific verb and resource, and the mention of compliance/debugging further clarifies its distinct role. It is easily distinguishable from sibling tools like get_jobs or get_queue_items.

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

Usage Guidelines4/5

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

The description provides a clear context by saying it is 'useful for compliance and debugging,' which signals appropriate use cases. However, it does not explicitly mention when not to use it or name alternative tools.

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