GenFlick

After an earlier inspect_asset step, record pass or rework for one clip's current keyframe sheet with the exact resource and revision and your visual findings

native.review_film_keyframes

DestructiveIdempotent

After an earlier inspect_asset step, record pass or rework for one clip's current keyframe sheet with the exact resource and revision and your visual findings. A pass releases that clip's videos the task held for this review. Changed inputs need a new inspection; automated critique is advisory.

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.review_film_keyframes"
  }
}

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

A3.9/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new consequences: a pass releases the clip's held videos, and stale inputs invalidate the decision. It does not address request_key idempotency or what the output schema reports on failure.

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?

Four short sentences with the prerequisite front-loaded and the consequence of a pass stated immediately after the action. Some redundancy with the title and a slightly overloaded first sentence ('with the exact resource and revision and your visual findings') cost it a point, but nothing is filler.

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?

An output schema exists, so return values need not be described, and the description covers the workflow anchor, the side effect, and the staleness rule for a nested six-parameter mutation. The remaining gap is the unexplained delegation/session parameters and no explicit pointer to the rework sibling.

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 reinforces that the resource and revision must be the exact ones inspected and that findings capture visual observations, which is useful meaning beyond the schema. However, work_id, delegation_id, request_key and expected_catalog_version receive no explanation in either the description or the schema, leaving real gaps.

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 (record pass or rework), a specific resource (one clip's current keyframe sheet), and the prerequisite step (an earlier inspect_asset). It is distinguishable from generic review siblings, but it never names the closest alternative, native.rework_film_keyframes, so an agent must still infer the boundary from the name alone.

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?

Gives explicit preconditions ('After an earlier inspect_asset step') and a clear when-not rule ('Changed inputs need a new inspection'), plus a note that automated critique is advisory rather than decisive. It stops short of routing to a named sibling for the rework path or explaining how this differs from native.rework_film_keyframes.

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?