Skip to main content
Glama

update_job

Modify an existing cron job's name, schedule, command, or enabled status to keep automated tasks correctly configured.

Instructions

Update an existing job (name, schedule, command, or enabled state).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
commandNo
enabledNo
scheduleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It never states whether omitted fields are left untouched or reset, whether changes are reversible, what permissions are needed, or what happens on an unknown id; it only implies "update" semantics.

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?

A single short sentence with the resource and affected fields front-loaded and no filler. There is nothing to trim, though the brevity comes at the cost of the missing semantics noted elsewhere.

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 5-parameter write operation with no annotations, no output schema, and no documented parameters, the definition is under-specified. An agent still cannot tell whether this is a partial patch, what id must reference, or how errors surface.

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%, so the description should compensate, but it merely repeats the self-descriptive parameter names (name, command, enabled, schedule). The required id parameter and the partial-vs-full update contract, the most consequential ambiguity for a 5-parameter mutation, go unexplained.

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?

"Update an existing job" gives a clear verb and resource, and the parenthetical enumerates the mutatable fields. It does not name a sibling or state how it differs from create_job or delete_job, so it stops short of a 5.

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?

There is no when-to-use guidance, no mention of prerequisites (the job must already exist), and no routing toward siblings such as create_job for new jobs or delete_job for removal. Usage is only implied by the word "existing".

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