GenFlick

Recover an original captured audience mutation after interrupted apply

native.genads_recover_audience_change

DestructiveIdempotent

Recover an original captured audience mutation after interrupted apply. This reads the original receipt and never calls the provider, repeats the change, resumes a stopped job or grants new authority.

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

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 real context beyond the annotations: it reads the original receipt, never calls the provider, and does not re-execute the mutation. However, annotations declare destructiveHint=true and readOnlyHint=false, and the description never explains what is actually consumed, invalidated, or marked recovered — it only lists what does not happen. The 'never calls the provider' line also sits in mild tension with openWorldHint=true, which the description does not reconcile.

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 tightly written sentences with the recovery condition front-loaded and no filler. The negation list in sentence two is packed but each clause earns its place by preempting a dangerous misread of the tool's authority.

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 core recovery semantics are stated. For a tool of this complexity — nested arguments, skill-hash proofs, catalog-version pinning, and a destructive annotation — the description omits prerequisites and side effects that an agent needs before calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters, five required, with only 50% schema description coverage and a nested required 'arguments' object. The description names no parameter at all and adds zero guidance on work_id, request_key idempotency semantics, or how expected_catalog_version should be sourced, so it fails to compensate for the undocumented half of the schema.

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?

Specific verb+resource+condition: 'Recover an original captured audience mutation after interrupted apply' tells an agent exactly which artifact is being recovered and under what circumstance. It is distinguishable from the write-path sibling native.genads_audience_change, though it never names that sibling explicitly, leaving the routing one small inferential step away.

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?

The trigger condition is stated clearly ('after interrupted apply'), and the second sentence supplies useful exclusions: it will not repeat the change, resume a stopped job, or grant new authority. What is missing is a positive pointer to the alternative tool to use when the apply was not interrupted (e.g. native.genads_audience_change) or when a new change is actually wanted.

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?