Meta Ads Targeting

meta-ads-targeting

Claude skills for pulling **real** Meta ad targeting IDs out of the Marketing API, validating them, and handing them to a Facebook Ads MCP as a CSV.

The problem this solves

Facebook Ads MCP servers can create ad sets but cannot look up targeting IDs. `ads_create_ad_set` says so directly:

Do NOT invent interest IDs — interest targeting requires real numeric IDs from the Facebook Targeting Search API.

So Claude can build you an ad set, but not populate its audience. This fills that gap.

There is a second, nastier problem. Most guides and blog posts tell you to browse the targeting catalogue with:

GET /search?type=adTargetingCategory&class=behaviors

**That endpoint does not exist.** It returns `400 · code 100 / subcode 33` on v12.0, v18.0 and v24.0, with or without a valid `ads_read` token, with or without the version segment. The error reads like a permissions problem, so people spend hours regenerating tokens that were never the issue. The working call is `/act_/targetingbrowse`, and `references/endpoints.md` documents it along with everything else that was verified live.

Install

/plugin marketplace add naz-geotrip/meta-ads-targeting
/plugin install meta-ads-targeting

What you get

Two skills, deliberately separate.

`meta-ads-app-setup` — runs once, ever

Creates a Business-type Meta app with the Marketing API use case, mints an `ads_read` token, picks your ad account, and writes the config. Also handles token-only regeneration later without touching the app.

Needs your browser, because Meta has no API for creating an app or minting a System User token. It asks permission before touching Chrome. Two steps are yours to click: a password confirmation and a permission dialog. Claude does neither on your behalf.

`meta-targeting-ids` — runs every time

Reads the config, retrieves IDs, validates them, writes a CSV, and recommends which to actually buy. Pure HTTP, no browser.

It is **hard-blocked fro