GenFlick

Read the saved catalog request and observation

native.genads_catalog_sync_request

DestructiveIdempotent

Read the saved catalog request and observation. Stopping a request does not stop the already enabled feed.

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

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

Behavior2/5

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

The description frames the tool as a 'read', yet annotations declare readOnlyHint=false and destructiveHint=true, so the framing understates the side effects the agent must plan for; this mismatch is the main transparency failure. The only real behavioral disclosure is the caveat that stopping a request does not disable an already enabled feed, which hints at persistent, non-reversible state but does not say what this specific call does to that state.

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?

Two short sentences with no filler, but the second sentence reads as a leftover caveat about a different operation and is not connected to what this tool actually does. The purpose statement is front-loaded but too thin to carry the weight.

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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. Still, for a tool with nested required arguments and a destructive hint, the description should at minimum clarify how this read relates to the enable/stop lifecycle it gestures at.

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?

Schema description coverage is only 50%, and three required parameters (work_id, request_key, and the nested arguments.store_id/operation_id) have no descriptions in either place. The description mentions none of the parameters, so it does not compensate for the coverage gap on a tool with a nested object and five required fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and a resource ('Read the saved catalog request and observation'), but 'catalog request' and 'observation' are undefined domain terms, and nothing distinguishes this from the crowded catalog family (genads_catalog_syncs, genads_catalog_sync_review, genads_check_catalog_sync, genads_read_catalogs). An agent cannot tell which of these returns the saved request state until it opens the schemas.

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 statement of when this tool should be used, no prerequisites, and no named alternative among the many catalog siblings. The second sentence addresses what happens after stopping a request, but never routes the agent toward or away from this tool in any concrete situation.

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?