Skip to main content
Glama

job_list

List jobs with optional filters such as process instance, job definition, exception presence, retries, and due date range, returning IDs, types, retry counts, due dates, and exception messages.

Instructions

List jobs with optional filters: process instance, job definition, exception presence, retries, and due date range. Returns id, type, retries, dueDate, and exceptionMessage.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNo
activeNo
jobIdsNo
sortByNo
timersNo
acquiredNo
dueDatesNo
messagesNo
sortOrderNo
suspendedNo
activityIdNo
executableNo
maxResultsNo
tenantIdInNo
createTimesNo
executionIdNo
firstResultNo
noRetriesLeftNo
withExceptionNo
jobDefinitionIdNo
withRetriesLeftNo
withoutTenantIdNo
exceptionMessageNo
failedActivityIdNo
processInstanceIdNo
processInstanceIdsNo
processDefinitionIdNo
processDefinitionKeyNo
priorityLowerThanOrEqualsNo
includeJobsWithoutTenantIdNo
priorityHigherThanOrEqualsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 schema fields changedv1.3.0
    • addedInput schema / properties / acquired
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / activityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createTimes
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueDates
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / exceptionMessage
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executable
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / failedActivityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / includeJobsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / jobDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobIds
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / messages
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / noRetriesLeft
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / priorityHigherThanOrEquals
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / priorityLowerThanOrEquals
      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 / processInstanceIds
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / suspended
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / timers
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withException
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withRetriesLeft
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.8/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 says this is a list operation and names some returned fields, but it omits pagination, sorting, defaults, permissions, and whether filters combine with AND or OR, which is significant for a 31-parameter endpoint.

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 sentences, front-loaded around listing jobs and returning fields. It contains no filler or repetition, though its brevity contributes to the completeness gaps in other dimensions.

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?

For a 31-parameter list endpoint with no annotations and no output schema, the description is far too sparse. It does not explain defaults, pagination, sorting, or most filters, though it does provide a partial list of returned fields.

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% for 31 parameters. The description covers only a handful of them: process instance, job definition, exception presence, retries, and due date range. It leaves many important parameters undocumented, including jobId, active, sortBy, maxResults, firstResult, tenant filtering, createTimes, and priority bounds.

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: list jobs. It also names representative filter axes and return fields. It does not explicitly distinguish itself from siblings such as job_get or job_count, but the list operation is clear.

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?

Gives no explicit when-to-use or when-not-to-use guidance. There is no mention of using job_get for a single job, job_count for counting, or jobDefinition_list for job definitions. The phrase 'optional filters' implies scoped listing but does not explain selection criteria.

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