GenFlick

generate series media

native.generate_series_media

DestructiveIdempotent

Queue explicitly standalone Media using destination=standalone_media. Images belonging to a named character, set or prop use save_element_file and generate_element_take on the existing element, followed by wait_for_jobs and read_element. This tool is not the default image destination. Supply destination, mode and prompt. Omit provider unless the creator requests a named model or the public_figure_likeness exception selects xai_grok_image_quality. Omit other settings to inherit saved values. To regenerate a file, supply its media_item_id; this adds a take without replacing its selected take. Documents are authored in Documents. Existing files are referenced by resource id (reference_resource_ids), never by URL.

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

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

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds meaningful context on top: omitted settings inherit saved values, and supplying media_item_id adds a take without replacing the currently selected one, which softens what the destructive hint implies. It does not say how the queued job completes or is polled, which matters for an async, open-world tool.

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?

Front-loaded with the destination constraint, then alternatives, then parameter rules; nearly every sentence carries a distinct rule. A few clauses are terse to the point of being cryptic ("Documents are authored in Documents") and the routing sentences interrupt the parameter guidance.

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 complex nested tool with an output schema, the description covers routing, required arguments, provider selection, reference-id discipline and regeneration semantics. The main omission is what happens after queueing — no pointer to job status or wait tools for this standalone path — which an agent needs to close the loop.

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% and several nested fields (title, prompt, aspect_ratio, image_quality, seedance_level) have empty descriptions, but the prose compensates: it names the three required arguments, gives a decision rule for provider and provider_selection_reason, and constrains reference_resource_ids to exact ids rather than URLs. The generic "omit other settings to inherit saved values" covers the undocumented remainder without enumerating it.

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?

Opens with a specific verb and resource ("Queue explicitly standalone Media") and pins the destination enum value, so the agent knows exactly what gets produced. It cleanly separates itself from the element-generation path (save_element_file / generate_element_take) but never mentions the sibling native.generate_series_images, leaving one obvious ambiguity unresolved.

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 an explicit negative rule ("This tool is not the default image destination"), an explicit routing rule for character/set/prop imagery with the exact alternative tool chain and follow-up calls (wait_for_jobs, read_element), and a routing note that documents belong elsewhere. When-to-use, when-not-to-use and alternatives are all present.

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?