GenFlick

Read the latest or exact saved Meta advertiser audience inventory

native.genads_read_audiences

DestructiveIdempotent

Read the latest or exact saved Meta advertiser audience inventory. Provider record IDs and platform targeting IDs are separate. Use platformId only for campaign inclusions/exclusions, with this saved operationId. Missing size or eligibility stays unavailable. This never refreshes, creates an audience or uploads people; request a fresh bounded inventory with genads_ad_action action audiences.

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

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

Behavior1/5

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

The description asserts non-mutating behavior ('This never refreshes, creates an audience or uploads people'), while annotations declare readOnlyHint=false and destructiveHint=true. An agent reading the prose would treat this as a safe read; the structured hints say the opposite, which is a direct conflict. The other useful disclosures (missing size/eligibility stays unavailable, provider IDs vs platform targeting IDs are distinct) are overshadowed by this contradiction.

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?

Five short sentences, purpose front-loaded, with the negative scoping ('never refreshes, creates...') and the sibling alternative in the final sentence. Some phrasing is terse to the point of ambiguity ('Missing size or eligibility stays unavailable'), but nothing is padded.

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 no prose, and the wrapper parameters with descriptions (read_skills, expected_catalog_version, publication_proposal_id) are documented in the schema. Still, for a six-parameter nested tool with a skills-proof and catalog-version contract, the description omits how 'latest' vs 'exact' is selected and gives no guidance on the required envelope parameters.

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

Parameters3/5

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

Schema coverage is 50% and neither account_id nor operation_id carries a schema description, so the description is expected to compensate. It explains the distinction between provider record IDs and platform targeting IDs and ties platformId to the saved operationId, but platformId is not a property in this schema, and the description never explains what operation_id does (presumably selecting 'exact' over 'latest').

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?

The description opens with a specific verb and resource: reading a 'saved Meta advertiser audience inventory', scoped as 'latest or exact'. That is far more precise than the bare tool name and hints at a two-mode read, though it does not explicitly separate itself from nearby siblings such as genads_audience_review or genads_audience_plans.

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?

It gives an explicit alternative for the case it does not cover: 'request a fresh bounded inventory with genads_ad_action action audiences'. It also constrains where platform targeting IDs may be used (campaign inclusions/exclusions). What it leaves implicit is how a caller chooses between 'latest' and 'exact' mode, presumably by supplying operation_id.

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?