Skip to main content
Glama

trigger_scheduled_job

Immediately execute a ServiceNow scheduled job on demand by sys_id, optionally as a background job that returns a job_id for polling. Requires WRITE_ENABLED=true.

Instructions

Immediately execute a scheduled job on-demand (requires WRITE_ENABLED=true)

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": {
      "sys_id": "<sys_id>"
    },
    "name": "trigger_scheduled_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
sys_idYesScheduled job sys_id to trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds one piece of value beyond those annotations: the WRITE_ENABLED=true gate that causes rejection. It does not mention the risk of duplicate runs from a non-idempotent fire, nor what the call returns.

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?

It is a single clause with the action front-loaded, and every phrase contributes: the effect, the immediacy, and the enabling prerequisite. No padding at all.

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

Completeness3/5

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

For a two-parameter mutation tool with full schema coverage, the definition covers the core action and the write gate. What is missing is a return-value hint (a run result vs. a job_id when async) and any note about repeated triggering creating duplicate runs.

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 sys_id and async are already documented, including the 20-second auto-switch to job mode and how to poll with get_job. The description adds no parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description names a specific verb and resource: 'Immediately execute a scheduled job on-demand.' That clearly distinguishes it from create_/get_/update_scheduled_job siblings, though it does not explicitly distinguish it from trigger_flow.

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 gives an implicit trigger condition ('on-demand', 'immediately') and a real prerequisite ('requires WRITE_ENABLED=true'), which tells the agent when it will fail. However, it never states when not to use it or which sibling to use instead, such as trigger_flow.

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