manage_jobs

Management

Manage Jobs

Inspect or cancel Scenario jobs. Actions: check, list, cancel. Args: - action: required — check, list, or cancel - job_id: required for check and cancel - filters, limit, pagination_token: optional for list - team_id, project_id: required for OAuth callers Returns: check returns full job details, list returns a summarized job array plus nextPaginationToken when available, and cancel returns the cancellation response. Examples: - "Check this job" -> action="check", job_id="job_xxx" - "List recent failed jobs" -> action="list", filters={"status": "failure"} - "Cancel this job" -> action="cancel", job_id="job_xxx" Don't use when: You need to start work. Use run_model, analyze, train, or manage_workflows instead.

open-world

Parameters

NameTypeRequiredDescription
actionenum(check | list | cancel)Job action: check, list, or cancel.
job_idstringJob ID. Required for check and cancel.
team_idstringTeam ID. Required if user belongs to multiple teams.
project_idstringProject ID to scope the operation to.
filtersunknownFilters for list action.
limitnumber20Results per page for list action.
pagination_tokenstringPagination token from a previous list response (nextPaginationToken).
response_formatenum(json | markdown)jsonOutput format: 'json' for structured data, 'markdown' for human-readable text.

Example Request

JSON
{
  "action": "list",
  "team_id": "team_abc123",
  "project_id": "proj_xyz789",
  "filters": {
    "status": "processing"
  },
  "limit": 20
}

Example Response

JSON
{
  "jobs": [
    {
      "jobId": "job_gen_123",
      "status": "processing",
      "type": "generate"
    }
  ]
}

Common Use Cases

  • Check the status of a long-running generation job by job ID
  • List recent jobs filtered by status to audit failed or cancelled runs
  • Cancel a generation job that is no longer needed