Meta Ads by Get MCP Ads

meta search targeting options

meta_search_targeting_options

Read-onlyIdempotent

Search Meta's read-only targeting metadata to find interests, validated interests, geographies, locales, countries, cities, regions, markets, or postal codes for ad targeting.

Instructions

Search Meta's read-only targeting metadata for interests, validated interests, geographies, locales, countries, cities, regions, markets, or postal codes.

Input Schema

Name	Required	Description
`type`	Yes	Provider object or operation type selected from this schema's allowed values.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`query`	No	Search text; required by most interest and geography searches
`countryCode`	No	Country code used to localize keyword or targeting results.
`locationTypes`	No	Location dictionary categories to include in targeting search.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

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 is fully covered. The description mostly repeats the read-only nature and lists resource categories rather than adding behavioral context such as pagination limits, rate limits, or empty-result behavior. With annotations carrying the behavioral burden, this is a limited contribution.

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?

The description is a single front-loaded sentence that begins with the action and resource. It is efficient and avoids low-value filler, though the enumerated list is somewhat long and could have been structured as use-case guidance instead.

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 and schema coverage is 100%, so return values and parameters need not be fully explained in prose. However, the description does not help an agent choose among the 17 type enum values or between this and sibling search tools, leaving a meaningful gap for a tool with such a large enum.

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 description coverage is 100%, so all five parameters are already documented in the input schema. The description hints at categories that map to the type enum, but it does not explain how to use query, countryCode, locationTypes, or limit beyond what the schema already states. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource ('Search Meta's read-only targeting metadata') and enumerates several domains such as interests, geographies, locales, and postal codes. It is clear what the tool returns in broad terms, though it does not explicitly distinguish itself from the closely named sibling meta_search_entities.

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

Usage Guidelines2/5

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

The description implies usage by listing targeting categories, but it never says when to choose this tool over meta_search_entities or other search siblings, nor when not to use it. There is no explicit guidance on prerequisites, required query text, or which targeting type to select for a given task.

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

Deploy Server