GenFlick

Save an enable, run or disable catalog plan

native.genads_save_catalog_sync_plan

DestructiveIdempotent

Save an enable, run or disable catalog plan. Enabling starts ongoing updates and daily removal of disappeared store items; disabling leaves existing catalog items. This saves a draft only. Use a complete saved advertiser catalog for enable or the native original sync ID for run/disable.

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

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

A3.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation risk is surfaced structurally. The description adds real value beyond that by describing the side effects of enabling (ongoing updates, daily removal of disappeared store items) versus disabling (existing items left alone) and by clarifying the call persists a draft only. No permission or version-conflict behavior is described, though the schema's expected_catalog_version implies optimistic concurrency.

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?

Four tight sentences with no repetition: purpose, effect of enable, effect of disable, draft-only caveat, then input requirements. Front-loaded and every clause carries information an agent needs.

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

Completeness4/5

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

For a destructive, versioned, draft-then-apply tool this covers mode semantics, side effects, and required input sourcing. With an output schema present, return values need not be explained. What is left thin is the session/version prerequisite chain implied by expected_catalog_version and read_skills, which the description does not tie into the workflow.

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

Parameters4/5

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

Schema description coverage is only 50%, and the description compensates by explaining the discriminator semantics of the `change` variant: enable takes a catalogId from a complete saved advertiser catalog, run/disable take the original syncId. That is meaning the anyOf branches in the schema cannot convey on their own. Remaining gaps (expected_catalog_version, read_skills) are partially documented in 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 (save) plus resource (catalog sync plan) and an explicit enumeration of the three plan kinds it handles (enable, run, disable). It does not name the sibling it differs from (native.genads_apply_catalog_sync), but 'This saves a draft only' effectively separates drafting from execution.

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?

Gives concrete input routing per mode: a complete saved advertiser catalog for enable, the native original sync ID for run/disable. The draft-only statement tells the agent it must not expect immediate effect. It stops short of naming which sibling to call next (apply/review) to execute the plan.

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?