Skip to main content
Glama

Croncool Cron Jobs

by cool.cron
OverviewDiscussionsAdmin

List scheduled cron jobs

list_jobs
Read-onlyIdempotent

Use this when the user wants to list scheduled jobs in CronCool to inspect schedules, enabled state and the latest execution status. Returns each job's id, name, schedule, target origin, method, enabled state and last run status and time, 20 per page by default, with a cursor for more. Not for a job's full run history.

Input Schema

NameRequiredDescriptionDefault
limitNoJobs per page, from 1 to 100; defaults to 20
cursorNoThe nextCursor of the previous page with the same projectId; absent for the first page
projectIdNoOnly jobs of this project

Output Schema

NameRequiredDescriptionDefault
jobsYesJob schedules and target origins only. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are excluded.
hasMoreYes
nextCursorYesCursor for the next page with the same filters; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque nextCursor from an earlier list_jobs call with the same project filter"New value: +"The nextCursor of the previous page with the same projectId; absent for the first page"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of jobs to return (default 20, max 100)"New value: +"Jobs per page, from 1 to 100; defaults to 20"
    • changedInput schema / properties / projectId / description
      Previous value: -"Only return jobs owned by this exact project id"New value: +"Only jobs of this project"
    • addedOutput schema / properties / jobs / description
      Added value: +"Job schedules and target origins only. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are excluded."
    • addedOutput schema / properties / nextCursor / description
      Added value: +"Cursor for the next page with the same filters; null on the last page"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds pagination behavior (20 per page by default, cursor for more) and enumerates the returned fields, which is useful context beyond the annotations, though it doesn't discuss ordering or rate limits.

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?

Three tight sentences with zero filler: trigger first, then return/pagination behavior, then the exclusion. Nothing is redundant and the important routing information is front-loaded.

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

Completeness5/5

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

An output schema exists, so the description needn't explain return values, yet it still summarizes them. Combined with pagination detail and the scope exclusion, an agent has everything needed to call this correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, cursor and projectId are already fully documented. The description restates the default page size and cursor semantics but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (list scheduled jobs in CronCool) plus the inspection goal (schedules, enabled state, latest execution status). It also explicitly carves itself away from the run-history sibling with 'Not for a job's full run history', so an agent can distinguish it from get_job_runs without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ('Use this when the user wants to list scheduled jobs...') and gives one clear exclusion ('Not for a job's full run history'). It stops short of naming the sibling tool to use instead, leaving the agent to infer get_job_runs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Croncool Cron Jobs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources