GenFlick

Read the latest or exact saved audience-change request and retained provider result for this advertiser and plan

native.genads_audience_change

DestructiveIdempotent

Read the latest or exact saved audience-change request and retained provider result for this advertiser and plan. A returned identity does not establish membership, consent or delivery. Missing description verification remains explicit.

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_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

C2.6/5.0

Behavior1/5

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

The name, title and description all frame this as a 'Read' of a saved request and retained provider result, yet annotations declare readOnlyHint=false and destructiveHint=true. That is a direct conflict in the safety profile an agent relies on before invoking. The description also offers no side-effect, auth, or precondition context that would reconcile the mismatch.

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

Conciseness3/5

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

Three sentences, no padding, and the core action leads. However, the trailing sentences ('A returned identity does not establish membership, consent or delivery. Missing description verification remains explicit.') are terse to the point of ambiguity and consume space that concrete usage or prerequisite guidance would have used better.

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 tool: six parameters, five required, nested arguments, and session-bootstrap requirements (work_id, read_skills, expected_catalog_version). An output schema exists so return values needn't be described, but the description leaves invocation preconditions and the destructive/read-only question unresolved, which is inadequate for 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 description coverage is 50%, with work_id, request_key, and the nested arguments object undocumented in the schema. The description partially compensates by tying 'advertiser and plan' to account_id/plan_id and 'latest or exact' to the optional operation_id, but it says nothing about work_id, request_key, or when publication_proposal_id matters.

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: 'Read the latest or exact saved audience-change request and retained provider result,' scoped to 'this advertiser and plan.' The 'latest or exact' phrasing distinguishes two retrieval modes. It does not name a sibling (e.g., native.genads_recover_audience_change or native.genads_audience_review) that an agent might confuse it with, so it stops short of 5.

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 or when-not-to-use guidance, no mention of prerequisites such as needing a bootstrapped session or valid catalog version, and no routing to alternatives like recover_audience_change or audience_review. The only hints ('latest or exact') are implicit and left for the agent to infer from the optional operation_id.

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?