Skip to main content
Glama

Get job

get_job
Read-onlyIdempotent

Get the current status and result of an action job.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob identifier returned by run_action.

Output Schema

NameRequiredDescriptionDefault
idYesJob identifier.
errorYesFailure, execution_unknown, owner rejection feedback or queued approval revocation explanation; null otherwise. Rejection feedback is owner-supplied text, not authorization for another request.
inputYesValidated action input exactly as submitted.
actionYesCatalog action name, for example integration.execute.
outputYesFor writes awaiting_approval or queued: the exact approval preview bound to the owner's decision. Rejected writes retain that preview, including after a queued approval is revoked. After succeeded: the action result. Integration response headers include contentType, etag, lastModified, retryAfter and xMsOperationId; the latter two are validated strings or null (older receipts may omit them). Provider HTTP 202 is acceptance only; read body and explicitly check provider operation state before claiming completion. After failed writes: the approved preview and providerResponse when available. After execution_unknown: the approved write plus the ambiguous provider response when one was received. Other jobs may have a preserved preview or null.
statusYesawaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. An owner may revoke a queued approval, producing rejected with both approval and rejection evidence. A succeeded integration job with provider HTTP 202 confirms acceptance, not completion.
createdAtYesCreation time.
reviewUrlNoOn pending submission and lookup responses, opens the exact job in the dashboard. Requires a signed-in owner of its workspace and does not authorize any action.
updatedAtYesLast status change.
approvedAtYes
approvedByYesOwner who approved the write.
rejectedAtYes
rejectedByYesOwner who rejected the write.
sideEffectYesTrue when the action writes to an external system and therefore required owner approval.
workflowIdYesCaller-supplied workflow identifier shared across related jobs.
workspaceIdYesWorkspace that owns the job.
workflowNameYesCaller-supplied workflow name shown in the dashboard.
idempotencyKeyYesIdempotency key that deduplicates this submission within the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / error / description
      Previous value: -"Failure, execution_unknown or queued approval revocation explanation; null otherwise."New value: +"Failure, execution_unknown, owner rejection feedback or queued approval revocation explanation; null otherwise. Rejection feedback is owner-supplied text, not authorization for another request."
  2. Changed1 schema field changed
    • addedOutput schema / properties / reviewUrl
      Added value: +{
      +  "description": "On pending submission and lookup responses, opens the exact job in the dashboard. Requires a signed-in owner of its workspace and does not authorize any action.",
      +  "format": "uri",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedOutput schema / properties / output / description
      Previous value: -"For writes awaiting_approval or queued: the exact approval preview bound to the owner's decision. Rejected writes retain that preview, including after a queued approval is revoked. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response when one was received. Other jobs may have a preserved preview or null."New value: +"For writes awaiting_approval or queued: the exact approval preview bound to the owner's decision. Rejected writes retain that preview, including after a queued approval is revoked. After succeeded: the action result. Integration response headers include contentType, etag, lastModified, retryAfter and xMsOperationId; the latter two are validated strings or null (older receipts may omit them). Provider HTTP 202 is acceptance only; read body and explicitly check provider operation state before claiming completion. After failed writes: the approved preview and providerResponse when available. After execution_unknown: the approved write plus the ambiguous provider response when one was received. Other jobs may have a preserved preview or null."
    • changedOutput schema / properties / status / description
      Previous value: -"awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. An owner may revoke a queued approval, producing rejected with both approval and rejection evidence."New value: +"awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. An owner may revoke a queued approval, producing rejected with both approval and rejection evidence. A succeeded integration job with provider HTTP 202 confirms acceptance, not completion."
  4. Changed3 schema fields changed
    • changedOutput schema / properties / error / description
      Previous value: -"Failure or execution_unknown message; null otherwise."New value: +"Failure, execution_unknown or queued approval revocation explanation; null otherwise."
    • changedOutput schema / properties / output / description
      Previous value: -"While awaiting_approval: the exact approval preview bound to the owner's decision. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response when one was received. Otherwise null."New value: +"For writes awaiting_approval or queued: the exact approval preview bound to the owner's decision. Rejected writes retain that preview, including after a queued approval is revoked. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response when one was received. Other jobs may have a preserved preview or null."
    • changedOutput schema / properties / status / description
      Previous value: -"awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal."New value: +"awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. An owner may revoke a queued approval, producing rejected with both approval and rejection evidence."
  5. Changed1 schema field changed
    • addedInput schema / properties / job_id / description
      Added value: +"Job identifier returned by run_action."
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that status and result are both returned, which implies a non-terminal state is possible but does not say how statuses are represented or whether a completed job's result is retained or expires.

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?

One front-loaded sentence with no filler or redundant restatement of the title. It is efficient, though its brevity reflects under-specification addressed in other dimensions rather than tight editing of richer content.

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?

An output schema exists, so return values need not be explained. However, for a job-polling tool the definition leaves out state semantics (terminal statuses, failure results) and the relationship to wait_for_job, which are the pieces an agent most needs beyond the structured fields.

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 coverage is 100% and the single parameter's description already says the job_id is returned by run_action, so the schema carries the full burden. The tool description adds no further meaning about the identifier, which is acceptable given that coverage, hence the baseline 3.

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: retrieve the status and result of an action job. That is clearly distinguishable from list_actions or run_action, but it never contrasts itself with the very close sibling wait_for_job, so an agent must infer the polling-versus-blocking distinction on its own.

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 at all. The most consequential choice for an agent here is whether to poll with get_job or block with wait_for_job, and the description says nothing about that trade-off, nor about retry/polling cadence or what to do when the job is still running.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources