Skip to main content
Glama

Cron List

cron_list

List Drupal cron jobs and see when cron last ran, so you can verify scheduled tasks without triggering them.

Instructions

List the jobs Drupal runs on cron, and when cron last ran.

In Drupal 8+ a "cron job" is a module implementing hook_cron; there is no job registry and no drupal_get_cron_jobs() - that Drupal 7 function is what this tool used to call, so it returned "Call to undefined function" on every site it has ever run against.

The implementations sit behind ModuleHandler::invokeAllWith(), whose callback is handed the listener without being forced to invoke it. Only $module is relied on: through Drupal 8-10 the callback receives ($function, $module, $arguments) and in Drupal 11 ($listener, $module), so the module is the second argument in every version, and never calling the first argument is what stops listing a job from running cron.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses critical behavioral context: that listing jobs does not run cron, and that the tool will not fail with 'Call to undefined function' on Drupal 8+ sites. It does not describe whether listing has side effects, permissions required, or output format, though an output schema exists.

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

Conciseness2/5

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

The description is excessively long for a zero-parameter list tool. Much of the text is internal Drupal implementation detail (hook_cron history, invokeAllWith callback signatures, Drupal 7 function references) that does not directly help an agent decide when or how to invoke the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values. It covers the core behavior and a key caveat about not executing cron, but omits practical info like required permissions or whether it works on all Drupal versions.

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

Parameters4/5

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

The input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters, and it appropriately focuses on behavior instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: 'List the jobs Drupal runs on cron, and when cron last ran.' This is a concrete read operation that an agent can distinguish from sibling tools like cron_run.

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 description does not explicitly say when to use this tool versus cron_run or drush_cron. However, the second sentence implicitly clarifies the usage scope by explaining the Drupal 8+ implementation model, which helps an agent understand that this tool lists rather than executes jobs.

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