GenFlick

Read 3D clips

native.read_film_three_d

DestructiveIdempotent

Read a Film's 3D-guided clips. For each clip: the part of the 3D cut it uses (cut-clock frames and shot names), its guide look and reference moment, the status of its image guide, motion guide and keyframe grid (ready, rendering, waiting for a render slot, failed with the reason, or not requested), how many of its shapes are linked, whether a newer version of the cut exists, and whether its video model can follow a motion guide. Compact by default; detail full for exactly one clip adds every shot use with its frames and each shape with its link. Changes nothing.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.read_film_three_d"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

C2.9/5.0

Behavior1/5

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

The description ends with 'Changes nothing,' directly contradicting annotations that declare readOnlyHint=false and destructiveHint=true. Beyond that clash, it discloses useful pipeline status vocabulary (ready, rendering, waiting for a render slot, failed with reason), but the explicit safety claim inverts what structured metadata says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, but a large share of the text is a long enumeration of return fields that duplicates the output schema. The final 'Changes nothing' clause is both wasteful and inaccurate given the annotations.

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 the field-by-field enumeration adds little, while genuinely complex invocation requirements (proof-of-skill array, catalog version sourcing) are not addressed at all. The description is complete on returned data but thin on what an agent must supply to call it successfully.

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 50%, and the description adds real meaning for one parameter: what 'detail: full' returns versus compact, including the 'exactly one clip' constraint. The session/wrapper parameters (read_skills, expected_catalog_version, request_key, work_id) go unmentioned in the description, leaving the caller to rely on partial schema text.

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?

States a specific verb and resource ('Read a Film's 3D-guided clips') and immediately distinguishes itself from the mutating siblings (edit_film_three_d_clip, render_film_three_d_guides) by enumerating read-only per-clip data. It never names which sibling to use instead, so the differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The only usage guidance is embedded in the behavior description: default is compact, and 'detail full for exactly one clip' expands each shot use and shape link. There is no guidance on when to choose this over native.inspect_film_three_d or native.read_film_color, nor on scoping by clip_ids vs scene_id.

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

All GenFlick tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?