Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_targeting_map

Resolve Meta ad targeting IDs into names, types, and paths so you can interpret IDs from other endpoints and apply targeting correctly.

Instructions

Map targeting IDs to their full details (names, types, paths). Useful for resolving IDs obtained from other endpoints.

Input Schema

NameRequiredDescriptionDefault
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
targeting_listYesJSON array of targeting IDs to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It conveys the operation is a lookup that resolves IDs to details (implicitly a safe read), but says nothing about behavior with unknown/invalid IDs, batch size limits, rate limits, or auth requirements.

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

Conciseness5/5

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

Two tight sentences with the core action front-loaded and the use-case hint following. No filler or redundancy; every clause earns its place.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must carry more weight. It partly compensates by naming the returned fields (names, types, paths) and the resolving use case, but omits limits on the input list and error handling for unresolvable IDs.

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 both account_id and targeting_list are already fully documented in the schema, including the env-var fallback for account_id. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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+resource: mapping targeting IDs to full details (names, types, paths). The parenthetical clarifies exactly what comes back, so an agent knows the return content. It does not, however, distinguish itself from the sibling search_targeting, which an agent could easily confuse with it.

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?

"Useful for resolving IDs obtained from other endpoints" gives a clear situational trigger for when to reach for this tool. It provides no exclusions and does not name search_targeting as the alternative for discovering IDs in the first place, so the routing is good but not fully disambiguated.

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

Deploy Server

Other Tools