GenFlick

Price the exact saved variant as video, or a PNG with output kind image and an exact zero-based frame

native.genads_quote_export

DestructiveIdempotent

Price the exact saved variant as video, or a PNG with output kind image and an exact zero-based frame. Returns a fingerprint, edit revision and credits; changed inputs require another quote.

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

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

B3.4/5.0

Behavior3/5

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

The description adds useful behavior beyond the annotations: what the response contains (fingerprint, edit revision, credits) and the invalidation rule that changed inputs require a new quote. But annotations declare destructiveHint=true and openWorldHint=true for what reads like a pricing call, and the description never explains what is destructive or what external state is touched — a notable gap given a quote operation is normally expected to be harmless.

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 dense sentences with no filler, and the output-mode distinction plus the response payload are front-loaded. The first sentence is slightly run-on (two alternatives stacked with 'or') but nothing is redundant enough to remove.

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?

The tool is a moderately complex 6-parameter, nested-schema call, and the output schema plus the description's mention of fingerprint/revision/credits cover return values adequately. What is missing is the workflow position — whether the quote must precede an export call, how request_key dedupes repeat quotes, and why a pricing call is flagged destructive — leaving the agent to infer the surrounding sequence.

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 compensates for the most confusing parameter by clarifying that 'image' output needs an exact zero-based frame. It says nothing about work_id, variant_id, request_key idempotency, or the read_skills/catalog-version proof fields, so several undocumented-adjacent parameters carry no added meaning.

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 uses a specific verb-resource pair ('Price the exact saved variant') and enumerates both output modes, so an agent knows this is a costing step for a saved GenAds variant, not the export itself. It does not name the sibling it hands off to (native.genads_export / native.genads_export_pack), so sibling differentiation is only implied.

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?

'Changed inputs require another quote' implies the quote is a prerequisite gate before export and must be refreshed on any input change, which is real usage context. However, it never states when to call this versus native.genads_export, native.genads_export_pack, or native.genads_quote_generation, nor what to do if a quote is still valid.

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?