Skip to main content
Glama

history_listJobLogs

Query historic job execution logs for a process instance to inspect timestamps, job types, retry counts, and exception details.

Instructions

Query historic job execution logs for a process instance. Returns log entries with timestamp, job type, retries, and exception details.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNo
logIdNo
sortByNo
hostnameNo
sortOrderNo
failureLogNo
maxResultsNo
successLogNo
tenantIdInNo
creationLogNo
deletionLogNo
firstResultNo
activityIdInNo
deploymentIdNo
executionIdInNo
jobDefinitionIdNo
withoutTenantIdNo
jobDefinitionTypeNo
processInstanceIdNo
failedActivityIdInNo
jobExceptionMessageNo
processDefinitionIdNo
processDefinitionKeyNo
jobDefinitionConfigurationNo
jobPriorityLowerThanOrEqualsNo
jobPriorityHigherThanOrEqualsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv1.3.0
    • addedInput schema / properties / activityIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / creationLog
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / deletionLog
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / deploymentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / failedActivityIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / failureLog
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / hostname
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionConfiguration
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobExceptionMessage
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobPriorityHigherThanOrEquals
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / jobPriorityLowerThanOrEquals
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / logId
      Added value: +{
      +  "type": "string"
      +}
    • 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 / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / successLog
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields (timestamp, job type, retries, exception details), but says nothing about read-only behavior, pagination, sorting defaults, permissions, or how the many filters affect results.

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?

The description is two sentences, front-loaded with the core purpose and return fields. It contains no filler or redundancy, though its brevity is also part of why the tool is under-specified for a 26-parameter query.

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 26 optional parameters, no annotations, no output schema, and 0% schema description coverage, the description is not complete enough. It identifies the resource and some return fields but omits filtering semantics, pagination, sorting behavior, and any operational constraints.

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

Parameters1/5

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

There are 26 parameters with 0% schema description coverage, and the description does not explain any of them. It does not clarify what failureLog, successLog, creationLog, deletionLog, sortBy, sortOrder, maxResults, firstResult, or the various ID filters do, leaving parameter meaning entirely undocumented.

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 states a specific verb and resource: 'Query historic job execution logs for a process instance.' It is clear enough to distinguish historic job logs from general job tools, but it does not explicitly name a sibling alternative such as job_list or history_listIncidents, so sibling differentiation is left implicit.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no alternatives. It implies the tool is for historic job logs on a process instance, but an agent must infer when to choose it over job_list, job_get, or other history_list tools.

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