GenFlick

Read a page of saved GenAds resources

native.genads_list

DestructiveIdempotent

Read a page of saved GenAds resources. Choose resources semantically; cursor is an exact returned ID.

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

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.4/5.0

Behavior1/5

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

The description frames this as a plain read ('Read a page of saved GenAds resources'), while the annotations declare readOnlyHint=false and destructiveHint=true. That is a direct and consequential inconsistency about whether the call can mutate state, and the description adds nothing about the required work_id/catalog-version provenance or the openWorldHint=true external reach. Under the rules, a description that contradicts annotations scores 1.

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, and the core operation is front-loaded. However, the second sentence is cryptic shorthand ('Choose resources semantically') that reads as under-specification rather than economy, so brevity does not buy clarity here.

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

Completeness5/5

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

Placeholder.

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%, so the description must compensate and largely does not. It clarifies one thing well — that the cursor is 'an exact returned ID' for the `after` parameter — but says nothing about `kind` (the semantically chosen resource type), `work_id`, `request_key`, or `read_skills`, the last of which the schema documents only in a single dense sentence.

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?

It states a verb plus resource ('Read a page of saved GenAds resources') and adds pagination scope, so the basic operation is identifiable. But 'resources' is left generic: the schema reveals seven distinct kinds (brief, concept, variant, source, experiment, media, pack) that the description never names, and among dozens of native.genads_* siblings it does not say what makes this list tool distinct from, e.g., native.genads_list_targets or native.list_genads_projects.

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?

'Choose resources semantically; cursor is an exact returned ID' gives a hint about how to page, but there is no when-to-use, when-not-to-use, or named alternative. An agent has no guidance on whether to start here versus native.genads_read_project or native.genads_documents when it needs a specific record.

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?