GenFlick

Read an exact collection approval, safe counts, current consent, qualification and original request

native.genads_lead_collection

DestructiveIdempotent

Read an exact collection approval, safe counts, current consent, qualification and original request. A completed page sequence describes returned submissions, not qualified leads or attributed sales. Use genads_ad_action action lead_collect with these exact collectionId and fingerprint references only when requested. A collection has one accepted request and cannot silently extend retention or recur.

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

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?

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description's leading verb is "Read" and nothing in the text warns the agent that the call is non-read-only or destructive in any way. It does add genuine behavioral context ('one accepted request', 'cannot silently extend retention or recur'), but that constraint frames the collection's lifecycle rather than disclosing what this invocation destroys or mutates.

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 with no padding, but it is not front-loaded on what the tool returns or when to call it, and dense phrasing like 'safe counts' and 'exact collection approval' is never unpacked. The middle sentence about page sequences versus qualified leads reads like a caveat for a sibling tool rather than this one.

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?

An output schema exists, so return values need not be described, but for a 6-parameter, nested-object, destructive-flagged tool the description omits prerequisites, what 'approval' and 'safe counts' mean, and any safety profile. Given the complexity and the misleading 'Read' framing against destructiveHint=true, an agent lacks what it needs to call this safely.

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 it only echoes collection_id via 'these exact collectionId and fingerprint references'. It says nothing about account_id, work_id, or request_key, and the 'fingerprint' terminology in the description has no corresponding parameter in the schema, which can actively mislead.

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 names the resource (a collection approval, counts, consent, qualification, original request) but as a noun pile without a clean verb-object mapping, so an agent cannot crisply state what payload comes back. It never distinguishes itself from the very similar siblings native.genads_lead_collections and native.genads_recover_lead_collection, which is the main ambiguity for selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use genads_ad_action action lead_collect with these exact collectionId and fingerprint references only when requested" gives a conditional and points at a related tool, so there is implied usage context. However, that sentence routes to a different tool rather than explaining when to call this reader, and no exclusion against the plural collections list or the recover tool is given.

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?