GenFlick

Save a GenAds media

native.genads_save_media

DestructiveIdempotent

Save a GenAds media. Use the exact saved revision; zero creates a new resource. Reuse operation_id after an uncertain response.

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

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the description is not responsible for the safety profile. It does add useful context on revision semantics and retry-by-operation_id behavior, but says nothing about what a destructive save overwrites, what happens on a revision conflict, or how publication_proposal_id approval interacts with the write.

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?

Three short sentences with no filler, and the revision rule is front-loaded immediately after the purpose statement. Every sentence carries operational information.

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?

Output schema exists, so return values need no explanation, but this is a destructive nested-body save with six parameters and the description omits conflict behavior, how it relates to sibling save tools, and the role of read_skills/catalog version beyond what the schema notes provide. Adequate but with clear gaps for a tool of this complexity.

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%, and the description adds meaning only for expected_revision (zero means create) and operation_id (reuse for retries). It is silent on work_id, request_key, and the relationship between arguments.id and the nested body, leaving several undocumented top-level parameters to the schema alone.

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 ('Save a GenAds media'), so the basic action is unambiguous. However, it does not distinguish this from the many nearby save siblings such as save_genads_variant, save_genads_pack, or save_genads_concept, leaving the agent to infer which record type this tool targets.

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?

It supplies two narrow usage rules: a zero expected_revision creates a new resource, and operation_id should be reused after an uncertain response. There is no guidance on when to choose this tool over the other GenAds save tools, nor any prerequisite or call-ordering advice.

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?