Skip to main content
Glama

jobDefinition_list

List and filter timer and async service task job definitions, including suspension state and override priority, to inspect or troubleshoot scheduled and asynchronous work.

Instructions

List job definitions with filters. Returns timer and async service task definitions with their current suspension state and override priority.

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

Input Schema

NameRequiredDescriptionDefault
activeNo
sortByNo
jobTypeNo
sortOrderNo
suspendedNo
maxResultsNo
tenantIdInNo
firstResultNo
activityIdInNo
jobDefinitionIdNo
withoutTenantIdNo
jobConfigurationNo
processDefinitionIdNo
processDefinitionKeyNo
withOverridingJobPriorityNo
includeJobDefinitionsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv1.3.0
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / activityIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / includeJobDefinitionsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / jobConfiguration
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobType
      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 / 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 / withOverridingJobPriority
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this is a read/list operation and describes the payload contents (timer and async service task definitions with suspension state and override priority), which substitutes partially for the absent output schema. However, it says nothing about pagination (maxResults/firstResult exist), result ordering, volume, or permissions — material for a 16-parameter listing tool.

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 sentences, no filler, and the core purpose is front-loaded before the return-value detail. Nothing is wasted, though the brevity is partly the cause of the coverage gaps rather than a virtue in itself.

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?

With 16 undocumented parameters, no annotations, and no output schema, this tool needs substantially more guidance than two sentences. The return-value sentence is a genuine help, but the parameter surface and pagination behavior are left entirely to inference.

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 16 parameters, so the description must compensate and largely fails to. It only obliquely gestures at two of them via 'suspension state' (suspended) and 'override priority' (withOverridingJobPriority); the remaining fourteen — active, jobType, tenant scoping, activityIdIn, processDefinitionId/Key, jobConfiguration, sort controls — receive no explanation of accepted values or semantics.

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 job definitions) and then clarifies what a 'job definition' actually is — timer and async service task definitions — which is the key distinction from the sibling job_list that operates on job instances. It stops short of naming job_list or jobDefinition_get explicitly, so the 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?

The phrase 'with filters' hints that this is a query tool, but there is no statement of when to choose this over job_list, jobDefinition_get, or job_count, and no note that all parameters are optional so an unfiltered call returns everything. The agent must infer selection criteria from sibling names alone.

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