GenFlick

Apply only the original encrypted pages already captured for this approved collection

native.genads_recover_lead_collection

DestructiveIdempotent

Apply only the original encrypted pages already captured for this approved collection. Never fetches additional pages, resumes Stop, reveals contacts or restores revoked or expired keys. Current private lead permission and original human consent remain mandatory.

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

B3.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the bar is lower, yet the description still adds real content: it will not fetch additional pages, will not resume a Stop, will not reveal contacts, and will not restore revoked or expired keys, plus it names two live authorization preconditions. That is meaningful boundary disclosure beyond the annotations, with only the outcome of a successful apply left unstated.

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

Conciseness4/5

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

Two sentences with the constraint front-loaded and no filler; every clause carries a distinct prohibition or precondition. The phrasing "resumes Stop" is compressed to the point of ambiguity, but the structure itself is efficient.

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

Completeness3/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 explained, and the authorization preconditions are covered. However, for a destructive, open-world mutation with nested arguments, the description never says what applying the captured pages actually produces or what happens to the collection afterwards, leaving the core effect underspecified.

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?

Six parameters at 50% schema description coverage, and the description contributes nothing about work_id, arguments.operation_id, or request_key, nor does it explain how "this approved collection" maps onto operation_id. With the uncovered half of the schema and no compensating text, an agent gets no help interpreting the identifiers it must supply.

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 first sentence is a verbatim restatement of the title and uses an odd verb ("Apply ... pages") rather than stating the operation as a recovery of a lead collection, which is what the name implies. The negative clauses do narrow the scope to a bounded, already-captured collection, but nothing distinguishes it from siblings such as native.genads_lead_collection, native.genads_recover_lead_form_change, or native.genads_deliver_leads.

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?

"This approved collection" and the prerequisite sentence imply the context in which the tool is legal (existing approved collection, current permission, original consent), and the "Never ..." list functions as partial when-not guidance. There is no explicit statement of when to choose this over the other lead-related recovery/list tools, and no mention of what to do if the prerequisites fail.

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?