Skip to main content
Glama

history_listUserOperations

Query the user operation audit log to identify who performed claim, complete, or delete actions, on which entity, and when.

Instructions

Query the user operation audit log. Returns who performed what operation (claim, complete, delete) on which entity and when.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNo
sortByNo
taskIdNo
userIdNo
batchIdNo
categoryNo
propertyNo
sortOrderNo
categoryInNo
entityTypeNo
maxResultsNo
executionIdNo
firstResultNo
operationIdNo
deploymentIdNo
entityTypeInNo
operationTypeNo
afterTimestampNo
caseInstanceIdNo
externalTaskIdNo
beforeTimestampNo
caseExecutionIdNo
jobDefinitionIdNo
caseDefinitionIdNo
processInstanceIdNo
processDefinitionIdNo
processDefinitionKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv1.3.0
    • addedInput schema / properties / afterTimestamp
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / batchId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / beforeTimestamp
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseExecutionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / categoryIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deploymentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / entityType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / entityTypeIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / externalTaskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / jobDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / operationId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / operationType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / property
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / userId
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It tells us this is a read (implied by 'Query'/'Returns') and describes the record contents, but says nothing about pagination (maxResults/firstResult are present in the schema), default sort order, result limits, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the resource and return shape front-loaded and no filler. It is efficient, though its brevity comes at the cost of the missing parameter and behavior detail noted elsewhere.

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?

A 27-parameter, annotation-free, output-schema-free query tool warrants far more than two sentences. The description leaves paging, sorting, filter semantics, and the read-only nature unexplained, which is a serious gap for an agent trying to build a correct query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 27 parameters at 0% schema description coverage, the description must compensate and does not. Only 'operationType' (claim, complete, delete), 'userId', entity, and time-window concepts are loosely hinted at; the bulk of the filters (jobId, batchId, categoryIn, executionId, sortBy, sortOrder, paging) are entirely undocumented anywhere.

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?

States a specific verb and resource ('Query the user operation audit log') and even enumerates the operation types (claim, complete, delete) plus the return shape. It does not differentiate itself from siblings such as history_listActivityInstances or migration_listAuditEntries, so an agent must infer which audit-style listing to pick.

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 phrase 'user operation audit log' implicitly signals usage for auditing who did what, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many history_* and migration_listAuditEntries siblings. Guidance is only implied.

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

Deploy Server

Other Tools