pipeline_schedule_get
Read one project-bound pipeline schedule, including revision, timing, policy, and latest run state.
When to use it
Use pipeline_schedule_get to inspect a pipeline schedule. On the workspace endpoint, pass projectId from project_list. On a project-scoped endpoint, the project is already bound: omit that argument and use the schema discovered from that endpoint.
Arguments
| Name | Type | Required | Default | Constraints |
|---|---|---|---|---|
pipelineId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
scheduleId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
projectId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.
Response shape
The implementation constructs payloads using these fields: schedule. The returned fields depend on the execution path.
MCP returns a text block containing the JSON operation result and a
structuredContent copy. The envelope includes data, completeness,
truncated, freshness, and warnings. Depending on the operation it can also
include nextCursor, evidence, job, or receipt.
Check those fields before treating a conversational summary as the result.
When a job is returned, inspect its status with the appropriate execution tool;
a queued response is not confirmation that work finished. Follow evidence links
when checking the underlying records.
Input methods
This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.
Use Semogram’s pipeline_schedule_get tool to inspect a pipeline schedule. Confirm the workspace and use records I can access. Do not change anything.
Choose the project explicitly before making this request. Use real resource IDs returned by earlier reads; a resource name is not a UUID. Do not fill missing business inputs with invented values.
This is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "pipeline_schedule_get",
"arguments": {
"pipelineId": "<PIPELINE_ID_UUID>",
"scheduleId": "<SCHEDULE_ID_UUID>",
"projectId": "<PROJECT_ID_UUID>"
}
}
}FAQ
What access and approvals are required?
Required permission scopes: pipelines:read.
OAuth uses current workspace membership; API keys use their assigned scopes
and grants. Discovery can exclude tools the caller cannot use.
Read-only annotation: Yes. Destructive annotation: No. Follow the operation’s declared contract and any applicable server-side approval policy.
How should I handle retries?
Do not assume repeated calls are safe merely because the client offers Retry. Inspect the result or existing request before repeating work that changes state. For 429 responses, honor Retry-After rather than retrying immediately.
Why is this tool missing or returning an error?
Confirm the workspace, resource IDs, and permission scopes. Read the returned error before changing the request. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.