Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

targeting_search

Read-onlyIdempotent

Search Meta ad targeting options by interests, locations, locales, or categories to build campaign and ad set audiences. Use query filters and limits to find valid targeting criteria.

Instructions

Search targeting options: interests, locations, locales, or categories.

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": {
      "type": "<type>"
    },
    "name": "targeting_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
typeYes
extraNoMore search parameters, for example location_types or class.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds only that results are reference data across four domains, but says nothing about result volume, the 1-500 limit ceiling, or how behavior varies by `type` — behavior beyond the annotations is essentially undisclosed.

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?

A single, front-loaded sentence with no filler or redundancy. Brevity is appropriate, though it is terse enough that it borders on under-specification rather than pure concision.

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?

Four parameters including a free-form nested object, no output schema, and ungated reads — this needs more than one sentence. Missing how `extra` keys vary per type, what a result record looks like, and how paging/limits interact, leaving an agent to guess at call construction.

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 low (25%) with a nested `extra` object, so the description must compensate. It maps some enum meanings to plain words (interests/locations/locales/categories) but never names `q`, `limit`, or `extra`, and does not explain that `extra` fields (location_types, class) depend on the chosen `type`.

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 ("Search") and resource ("targeting options") and enumerates the domains searched: interests, locations, locales, categories. It does not differentiate itself from siblings like get/list, and it omits the fifth enum value (adinterestsuggestion), so an agent cannot fully infer scope from the description alone.

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?

Usage is only implied: an agent can infer it should call this when resolving ad targeting values, but there is no explicit when-to-use vs. when-not, no mention of preferring `get`/`list` for already-known IDs, and no prerequisite or rate-limit context.

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