GenFlick

Save a media in a linked GenAds project using its native command and exact observed revision

native.save_genads_media

DestructiveIdempotent

Save a media in a linked GenAds project using its native command and exact observed revision. Zero creates a resource.

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_genads_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.

Changed3 schema fields changedNov 5, 2026
- addedInput schema / properties / arguments / properties / body / properties / settings / default / seedanceLevel
```
Added value: +"mini_480p"
```
- addedInput schema / properties / arguments / properties / body / properties / settings / default / videoQuality
```
Added value: +"draft"
```
- addedInput schema / properties / arguments / properties / body / properties / settings / default / videoResolution
```
Added value: +"480p"
```
First observedNov 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is largely supplied. The description adds genuinely new behavior: the save is a compare-and-set against an 'exact observed revision' and revision zero creates rather than updates. It still does not say what happens on a revision mismatch, what existing data is overwritten, or what permissions the linked project requires.

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?

Two short sentences with zero filler, and the creation semantics are front-loaded where the agent will read them. The terseness is close to under-specification for a destructive, deeply nested tool, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex mutation tool with six parameters, a deeply nested body including settings, and destructive semantics, yet the description covers only the revision rule. An output schema exists, so return values need not be explained, but failure modes (stale revision), sibling disambiguation, and the meaning of work_id/request_key are all missing. For a destructive, open-world write, that is a significant gap.

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%, with descriptions present for read_skills, publication_proposal_id, and expected_catalog_version. The description adds meaning to the unconcealed expected_revision parameter by stating it must be the exact observed revision and that zero creates a resource. It adds nothing for work_id, request_key, or the large nested body/settings object, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Save a media in a linked GenAds project') and disambiguates the create-vs-update ambiguity with 'Zero creates a resource.' It stops short of distinguishing this tool from the closely related sibling native.genads_save_media, which an agent could easily confuse with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative. Given that a nearly identically named sibling (native.genads_save_media) exists alongside save_genads_brief/concept/pack/variant/source, the absence of routing guidance leaves the agent to infer selection from the name alone.

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?