Skip to content
AdlyseMCP Docs
Product guideMCP reference
⌘K
Open Adlyse
⌘K
Overview
QuickstartAuthentication
adlyse-insights
adlyse-reports
adlyse-ads
adlyse-workflows
list_workflowsget_workflowrun_workflowget_run_status
adlyse-adminadlyse-all
  1. Overview
  2. adlyse-workflows

get_schedule

One schedule, with its recent runs — how you check whether a scheduled agent actually ran.

Parameters#

NameTypeRequiredDefaultDescription
schedule_idstringyesThe schedule id (e.g. sched_abc123)
include_runsbooleannotrueInclude the 10 most recent runs and their status

Returns#

json
{
  "schedule": {
    "schedule_id": "sched_abc123",
    "human_readable": "Every weekday at 7:00 AM (America/Los_Angeles)",
    "status": "active",
    "target_type": "assistant",
    "target_name": "Pacing analyst"
  },
  "recent_runs": [
    {
      "id": "sched_run_xyz",
      "status": "completed",
      "created_at": "2026-08-18T07:00:02-07:00",
      "started_at": "2026-08-18T07:00:03-07:00",
      "completed_at": "2026-08-18T07:01:40-07:00",
      "duration_seconds": 97.2,
      "error": "",
      "thread_id": "thread_abc123",
      "agent_run_id": null,
      "batch_job_run_id": null,
      "result_tool": "get_assistant_run"
    }
  ]
}

Each run names what it executed: an agent target carries thread_id (read it with get_assistant_run), a workflow target carries agent_run_id (read it with get_run_status). result_tool says which.

Errors#

error_typeWhen
auth_errorMissing / invalid API key
not_foundUnknown schedule id, or one outside your organization