Skip to main content
Glama

Check a run

get_run
Read-onlyIdempotent

Check a MakeViral run started with run_template: its status, minutes left, and the finished video or photo link when it is ready. With wait true the call waits up to 40 seconds for the run to finish, so you can wait for the result in the same answer and then give the user the link.

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": {
      "runId": "<runId>"
    },
    "name": "get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to 40 seconds for the run to finish before answering. Default false.
runIdYesThe run id from run_template, e.g. 'tr_ag...'

Output Schema

NameRequiredDescriptionDefault
runYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / run / properties / saveUrl
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds the genuinely useful trait that wait=true blocks up to 40 seconds. It doesn't mention polling cadence or failure/error states, so not a 5.

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?

Two sentences, front-loaded with the returned fields and followed by the one non-obvious behavior (blocking wait). No filler.

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

Completeness5/5

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

Output schema and annotations carry return shape and safety profile, and the description covers the only surprising behavior (40s blocking). Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes beyond it by explaining *why* wait exists ('wait for the result in the same answer') and anchoring runId to 'from run_template'. Still no default or format elaboration beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Check a MakeViral run started with run_template', and enumerates exactly what it returns (status, minutes left, finished video/photo link). The 'started with run_template' tie-back makes it trivially distinguishable from list_runs and get_creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly situates the tool: use it after run_template to poll a specific run ID, and use wait=true to block for the result in one turn. It does not explicitly name the alternative (list_runs) or state when not to use it, which keeps it short of a 5.

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