GenFlick

apply visual program

native.apply_visual_program

DestructiveIdempotent

Apply an ordered finish to an exact picture, or place a generated clip/overlay at that picture. Supply the current expected_spec_hash. placement defaults to finish; clip/overlay takes one corresponding instance (id, role and its pinned revision reference; version, enabled, seed, clock, assets and params default) and duration_seconds. Clip position before/after defaults to before and ripples the cut. material applies glyph effects to an exact native text overlay item_id. Empty finish/material clears its stack. Empty programs with placement clip or overlay and item_id the placed generated clip's or overlay's own id takes it off the cut.

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

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.7/5.0

Behavior4/5

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

Beyond the annotations (destructive/idempotent/openWorld), the description discloses concrete mutation behavior: it requires the current expected_spec_hash, an empty finish or material clears its stack, an empty program with clip/overlay removes the placed item from the cut, and a before/after clip position 'ripples the cut'. That is meaningful side-effect disclosure the annotations alone do not convey.

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?

The main purpose is front-loaded and no sentence is clearly padding, but the body is a chain of semicolon-joined clauses that is hard to parse, and phrases like 'version, enabled, seed, clock, assets and params default' are a noun wall. It would benefit from breaking the mode behaviors into short parallel statements.

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?

For a multi-mode mutation tool with an output schema, the description covers the core behaviors, the concurrency guard, and the destructive empties/removal cases. It omits prerequisites such as the required native skill proofs in read_skills and the catalog version, which an agent must satisfy before calling, leaving a small completeness gap.

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 only 50%, but the description compensates well: it explains placement semantics and its default, that clip/overlay takes one instance with id, role and pinned revision reference while version/enabled/seed/clock/assets/params default, the role of duration_seconds, position defaults to before, and item_id semantics for material and for removal. The envelope parameters (work_id, read_skills, expected_catalog_version, request_key) get no explanation here, so it is not complete.

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?

The opening sentence gives a specific verb and resource ('Apply an ordered finish to an exact picture, or place a generated clip/overlay at that picture') and the placement modes (finish, clip, overlay, material) enumerate what the tool can do. It does not name its nearest siblings (build_visual_program, write_visual_program_draft, inspect_visual_program), so the boundary against those is left implicit.

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?

Mode selection is partially explained ('placement defaults to finish', clip/overlay takes an instance, material targets a text overlay item_id), which implies when each mode applies. There is no explicit when-not guidance and no routing statement distinguishing it from build_visual_program or write_visual_program_draft in the sibling set.

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?