Skip to main content
Glama

history_listTaskInstances

Query historic task instances by process instance, definition key, assignee, or completion state to retrieve names, assignees, end times, durations, and process instance IDs.

Instructions

Query historic task instances by process instance, definition key, assignee, or completion state. Returns name, assignee, endTime, duration, and process instance ID.

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

Input Schema

NameRequiredDescriptionDefault
sortByNo
taskIdNo
assignedNo
finishedNo
taskNameNo
sortOrderNo
taskOwnerNo
maxResultsNo
tenantIdInNo
unassignedNo
unfinishedNo
executionIdNo
firstResultNo
taskDueDateNo
startedAfterNo
taskAssigneeNo
taskNameLikeNo
taskPriorityNo
finishedAfterNo
startedBeforeNo
taskOwnerLikeNo
taskVariablesNo
caseInstanceIdNo
finishedBeforeNo
caseExecutionIdNo
processFinishedNo
taskDescriptionNo
withoutTenantIdNo
caseDefinitionIdNo
processVariablesNo
taskAssigneeLikeNo
taskDeleteReasonNo
taskDueDateAfterNo
taskFollowUpDateNo
taskInvolvedUserNo
taskParentTaskIdNo
caseDefinitionKeyNo
processInstanceIdNo
processUnfinishedNo
taskDefinitionKeyNo
taskDueDateBeforeNo
taskInvolvedGroupNo
caseDefinitionNameNo
withoutTaskDueDateNo
processDefinitionIdNo
taskDefinitionKeyInNo
taskDescriptionLikeNo
withCandidateGroupsNo
activityInstanceIdInNo
processDefinitionKeyNo
taskDeleteReasonLikeNo
taskHadCandidateUserNo
processDefinitionNameNo
rootProcessInstanceIdNo
taskFollowUpDateAfterNo
taskHadCandidateGroupNo
taskFollowUpDateBeforeNo
withoutCandidateGroupsNo
variableNamesIgnoreCaseNo
variableValuesIgnoreCaseNo
processInstanceBusinessKeyNo
processInstanceBusinessKeyInNo
processInstanceBusinessKeyLikeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed63 schema fields changedv1.3.0
    • addedInput schema / properties / activityInstanceIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigned
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / caseDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseExecutionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / finished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / finishedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / finishedBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processFinished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / processInstanceBusinessKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processUnfinished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / processVariables
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / rootProcessInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startedBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskAssignee
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskAssigneeLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDefinitionKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDeleteReason
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDeleteReasonLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDescription
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDescriptionLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDueDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDueDateAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDueDateBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskFollowUpDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskFollowUpDateAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskFollowUpDateBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskHadCandidateGroup
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskHadCandidateUser
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskInvolvedGroup
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskInvolvedUser
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskOwner
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskOwnerLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskParentTaskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskPriority
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / taskVariables
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / unassigned
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / unfinished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / variableNamesIgnoreCase
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / variableValuesIgnoreCase
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withCandidateGroups
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutCandidateGroups
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTaskDueDate
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the behavioral burden, and 'historic' only weakly implies read-only. It says nothing about pagination (firstResult/maxResults are in the schema but unmentioned), default or configurable ordering (sortBy/sortOrder), result caps, or tenant scoping behavior. For a 63-parameter history query with zero annotation coverage this is a substantial gap.

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 front-loaded sentences with no filler: the first states the capability and filter axes, the second enumerates return fields. It is efficient, though the brevity is partly a byproduct of leaving the tool's real complexity undocumented.

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 63 optional parameters, no annotations, and no output schema, the definition is far too thin; only five return fields are described and paging/sorting behavior is absent. The one useful compensation is the explicit return-field list, which partially substitutes for a missing output schema.

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?

Schema description coverage is 0% across 63 parameters, so the description is the only source of meaning and it documents just four filter dimensions. Dozens of parameters — like-after/before date ranges, candidate group flags, variable filters, tenant flags, and the sort controls — receive no explanation, and no format or syntax hints (e.g., date format, comma-separated list handling) are provided.

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 names a specific verb and resource ('Query historic task instances') and lists the primary filter axes (process instance, definition key, assignee, completion state), which separates it conceptually from history_listProcessInstances and history_listActivityInstances. It stops short of explicitly naming those siblings, so differentiation is implied rather than stated.

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?

There is no when-to-use guidance: nothing says why an agent would pick historic task instances over runtime tasks (task_list) or over the process/activity history siblings, and no prerequisites or exclusions are given. The filter list hints at use cases but leaves selection between alternatives entirely to inference.

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