GenFlick

save element final prompt

native.save_element_final_prompt

DestructiveIdempotent

For an image, audio or video file, save an exact Final prompt edit, keep the existing edited text against current inputs, or rebuild from the current source. Documents and other files have saved content instead of generation prompts. First read the Final prompt and copy its file revision and input fingerprint. Saving never generates a take.

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_final_prompt"
  }
}

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

Behavior4/5

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

The annotations already disclose mutation, destructive, idempotent, and open-world traits. The description adds meaningful behavior: the three action modes, the read-before-save requirement, and the fact that saving never generates a take. It does not spell out exactly what prior prompt content is overwritten or how revision mismatches are handled, but it provides solid context beyond the annotations.

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

Conciseness5/5

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

Four tight sentences front-load the purpose, exclusions, precondition, and non-generation behavior. There is no filler, and each sentence contributes useful information for invoking the tool correctly.

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?

Given the tool's complexity, nested arguments, annotations, and output schema, the description covers the critical decision points: applicable file types, save modes, read-before-save precondition, and non-generation. It does not fully document all top-level parameters or destructive edge cases, but those are partly covered by the schema and annotations.

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?

With only 50% schema description coverage, the description compensates by explaining the action modes and tying edit/keep/rebuild to text and current inputs. It also explains that expected_revision and expected_input_fingerprint should be copied from a prior Final prompt read. It leaves work_id, element_id, file_id, and request_key to the schema or name, and only partially covers the remaining top-level parameters.

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 states a specific verb and resource and enumerates the three save modes: exact edit, keep existing edited text, or rebuild from source. It also limits scope to image, audio, and video files while excluding documents and other files. It does not explicitly name the read counterpart or other save siblings, so sibling routing is inferred rather than stated.

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 a clear precondition: first read the Final prompt and copy its file revision and input fingerprint. It also provides a useful exclusion by noting that documents and other files use saved content rather than generation prompts. It stops short of naming alternatives such as native.read_element_final_prompt or native.save_element_file, so the agent must still infer sibling choice.

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?