Skip to main content
Glama

Run image, video and audio nodes

playground_node_run
Idempotent

Run the generation already configured on 1–20 existing image, video or audio nodes. Image: prompt (its Text node), modelId, aspectRatio, wired references. Video: instructions, modelId, aspectRatio, duration, wired references and first/last frames. Audio: the node's own instructions (speech: the words; music: the lyrics), modelId (minimax:speech-2.8-hd, minimax:speech-2.8-turbo, minimax:music-2.5, minimax:music-1.5), voice (speech) or style (music) — set them with playground_canvas_apply_operations; wired Text nodes are refused for audio. Prompt Helper and Video Story nodes cannot run here (they run in the browser). quote: true returns a free, ten-minute quoteId and exact credits; execution requires that quoteId. It returns exact credits per node and spends nothing (canvas:read). Otherwise it requires project edit access and returns approval_required with exact scopes, fingerprints and credit ceilings for the user to review and confirm in this chat. After approval, poll playground_media_job_get or read playground_node_get. A retried idempotencyKey never charges twice.

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": {
      "projectId": "<projectId>",
      "nodeIds": "<nodeIds>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_node_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteNoWhen true, return pricing without executing paid generation; show the quote and obtain user approval before spending.
nodeIdsYesIDs of the existing canvas nodes to use for this action.
quoteIdNoRequired for execution: the unexpired quoteId returned by quote: true.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nextNoSuggested next action; it does not authorize spending.
errorNo
itemsNo
nodesNo
runIdNo
reasonNo
reviewNo
statusYes
balanceNo
creditsNo
nodeIdsNo
quoteIdNo
replayedNo
revisionNo
canvasUrlNo
expiresAtNoSerialized ISO timestamp.
projectIdNo
dispatchIdsNo
confirmationNo
totalCreditsNo
failedNodeIdsNo
validitySecondsNo
approvalLocationNo
completedNodeIdsNo
inputFingerprintNo
uncertainNodeIdsNo
sufficientCreditsNo
estimatedBalanceAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the spending model, the approval_required response with scopes, fingerprints and credit ceilings, the canvas:read versus project edit access distinction, and the ten-minute quote expiry. The idempotency note ('a retried idempotencyKey never charges twice') adds the cost consequence that idempotentHint alone does not convey. Minor gap: no statement of typical latency or failure modes beyond revision conflict.

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?

Information-dense and front-loaded, with the primary action first and pricing/approval flow after. The per-modality clauses and the parenthetical modelId enumeration make it long and slightly dense, but almost every clause carries distinct operational information.

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?

Given a mutating, credit-spending tool with an output schema, the definition covers prerequisites, authorization tiers, the approval round-trip, quoting, and where to poll afterward. Nothing an agent needs to invoke it safely 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 the baseline is 3, but the description adds real meaning: quote:true returns pricing without spending, quoteId is mandatory for execution and comes from that quote, and idempotencyKey reuse is cost-safe while a new key is needed after quoting or changing inputs. expectedRevision and nodeIds are left to their schema text.

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 concrete verb and resource with explicit scope: 'Run the generation already configured on 1–20 existing image, video or audio nodes.' It then enumerates what 'already configured' means per modality (image prompt/modelId/aspectRatio/references; video instructions/duration/frames; audio instructions/modelId/voice-style), so an agent can tell exactly which node types qualify.

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

Usage Guidelines5/5

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

Gives explicit routing: use quote:true to obtain a free ten-minute quoteId, execution requires that quoteId, and setting audio voice/style must be done first via playground_canvas_apply_operations. It names exclusions (Prompt Helper and Video Story nodes cannot run here) and post-execution alternatives (poll playground_media_job_get or read playground_node_get).

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.