GenFlick

save element file

native.save_element_file

DestructiveIdempotent

Create a named image, audio, video or document file, or edit an existing file with its current revision. A file stores its own source prompt and settings; saving does not generate. Existing Final prompt edits are preserved as construction updates automatically. Omit file_id to create; supply kind and name for creation.

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

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

Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description usefully adds that saving has no generation side effect and that existing Final prompt edits are preserved automatically as construction updates. However, given destructiveHint=true it never says what is overwritten or lost on edit, nor how revision conflicts behave, which is the main behavioral risk an agent needs covered.

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, front-loaded with the create/edit duality before the caveats. The closing sentence ('Omit file_id to create; supply kind and name for creation') partly restates the opening one, a small redundancy but not bloat.

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 return values need not be described, and the create/edit split is covered. For a destructive, idempotent mutation with nested arguments and 5 required parameters, though, the description omits overwrite semantics, revision-conflict failure modes, and most parameter roles, so it is only adequate rather than complete.

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 description coverage is 50%, and the description adds real meaning for file_id (omission means create) and expected_revision (edit against current revision), plus the role of kind/name in creation. It says nothing about the many undocumented fields — work_id, element_id, variant_id, role, settings, request_key — leaving half the parameters explained only by name.

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 description gives a specific verb and resource ('Create a named image, audio, video or document file, or edit an existing file') and clarifies that the object stores its own prompt and settings. It also draws the key boundary against generation tools with 'saving does not generate', though it never names the sibling it is contrasted with (e.g. native.generate_element_take).

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?

It gives explicit mode-selection rules: omit file_id to create, supply kind and name for creation, and supply the current revision to edit. It stops short of naming alternative tools (native.create_element, native.edit_element_file_references, native.save_element_final_prompt) or stating when not to use this tool.

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?