Skip to main content
Glama

Look at storyboard frames

view_storyboard_images
Read-only

Returns the first/last frame of each scene as images (downscaled) so you can judge product fidelity, continuity, text and scale before approving. Optionally restrict to scenes.

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": {
      "productionId": "<productionId>"
    },
    "name": "view_storyboard_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenesNo
maxEdgeNo
productionIdYesProduction ID (from list_productions or create_production).
includeSourcesNoAlso include the original product reference photos for comparison (first 2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the bar is lower; the description adds real value by disclosing that only first/last frames are returned, that images are downscaled, and that approval is the intended next step. It stops short of stating image count per scene or format details, 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 dense sentences with the return type, scope, and restriction option front-loaded. No filler, and the purpose clause does real work rather than restating the title.

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

Completeness4/5

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

With no output schema and a simple read-only operation, the description gives enough to call it correctly: what comes back, the per-scene granularity, and the optional filter. Only minor details like exact image count or resolution handling are left implicit.

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 50%, so the description must compensate and largely does: 'Optionally restrict to scenes' explains the scenes filter and 'downscaled' contextualizes maxEdge. includeSources and productionId are covered by schema descriptions, leaving only minor ambiguity about the downscale setting.

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 ('Returns the first/last frame of each scene as images') with scope (downscaled, per-scene) and the downstream purpose (judge fidelity before approving). An agent can distinguish it from view_media or run_quality_check because it names the exact artifact and the pre-approval moment.

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?

'before approving' gives a clear trigger context, and 'Optionally restrict to scenes' signals the narrowing option. It does not explicitly name alternatives (e.g. view_media for raw assets, approve_storyboard as the follow-up), so it falls just short of full when/when-not guidance.

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