Skip to main content
Glama

Targeting options

targeting_options
Read-onlyIdempotent

Looks up actual platform audience, interest, language or location IDs. A Meta custom audience comes with its kind, Meta's size estimate, retention, state and creation date. Returned candidates are not confirmed launch choices.

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": {
      "input": "<input>"
    },
    "name": "targeting_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / input / properties / kind / description
      Previous value: -"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-event, page-post: the instant forms, published Instant Experiences, upcoming events or latest posts of the Page given as query. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query. app: the apps it advertises, with stores and events."New value: +"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-post: the instant forms, published Instant Experiences or latest posts of the Page given as query. page-event: refused, Meta lets only its Marketing Partners list a Page's events; ask the person for the event's link. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query. app: the apps it advertises, with stores and events."
  2. Changed2 schema fields changed
    • changedInput schema / properties / input / properties / kind / description
      Previous value: -"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-event, page-post: the instant forms, published Instant Experiences, upcoming events or latest posts of the Page given as query. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query."New value: +"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-event, page-post: the instant forms, published Instant Experiences, upcoming events or latest posts of the Page given as query. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query. app: the apps it advertises, with stores and events."
    • changedInput schema / properties / input / properties / kind / enum
      Previous value: -[
      -  "catalog",
      -  "custom-audience",
      -  "detailed",
      -  "instant-experience",
      -  "interest",
      -  "language",
      -  "lead-form",
      -  "location",
      -  "page-event",
      -  "page-post",
      -  "product-set",
      -  "saved-audience"
      -]New value: +[
      +  "app",
      +  "catalog",
      +  "custom-audience",
      +  "detailed",
      +  "instant-experience",
      +  "interest",
      +  "language",
      +  "lead-form",
      +  "location",
      +  "page-event",
      +  "page-post",
      +  "product-set",
      +  "saved-audience"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / input / properties / kind / description
      Previous value: -"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-event: the instant forms, published Instant Experiences or upcoming events of the Page given as query. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query."New value: +"detailed: interests, behaviors and demographics. location: countries, regions, cities and postal codes. saved-audience: the account's saved audiences with their targeting. lead-form, instant-experience, page-event, page-post: the instant forms, published Instant Experiences, upcoming events or latest posts of the Page given as query. catalog: the catalogs a Sales campaign can run on. product-set: the product sets of the catalog given as query."
    • changedInput schema / properties / input / properties / kind / enum
      Previous value: -[
      -  "catalog",
      -  "custom-audience",
      -  "detailed",
      -  "instant-experience",
      -  "interest",
      -  "language",
      -  "lead-form",
      -  "location",
      -  "page-event",
      -  "product-set",
      -  "saved-audience"
      -]New value: +[
      +  "catalog",
      +  "custom-audience",
      +  "detailed",
      +  "instant-experience",
      +  "interest",
      +  "language",
      +  "lead-form",
      +  "location",
      +  "page-event",
      +  "page-post",
      +  "product-set",
      +  "saved-audience"
      +]
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context: for Meta custom audiences it enumerates the returned fields (kind, size estimate, retention, state, creation date) and warns the results are unconfirmed candidates — the latter is a real behavioral caveat an agent could otherwise misuse.

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?

Three front-loaded sentences with no filler: purpose first, return payload second, then a caveat. It could be slightly tighter, but every sentence contributes information an agent would act on.

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?

This is a complex tool — 13 kinds, nested input object, no output schema — but the description only describes the return shape for one kind (Meta custom audiences) and stays silent on what comes back for locations, interests, languages or the Page resources. The schema covers the rest, but the description leaves clear gaps for a lookup whose value is largely in what it returns.

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 75% and the enum description already documents most kinds in detail, so the schema carries most of the parameter burden. The description adds only the semantic that returned values are 'actual platform' IDs rather than hypothetical suggestions, with no clarification of platform, accountId, query, accountIds or userStatement.

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?

States a specific verb and resource ('looks up actual platform audience, interest, language or location IDs'), so an agent knows this is an ID-resolution lookup rather than a campaign builder or estimate tool. It doesn't name the close sibling audience_estimate or explain the boundary between them, so it falls short of full sibling differentiation.

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?

The closing caveat ('Returned candidates are not confirmed launch choices') implies this is a discovery step that precedes a launch, which is useful implied guidance. But there is no explicit when-to-use / when-not-to-use rule and no routing to an alternative when the agent needs confirmed choices or size estimates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.