Meta Pages

Lists the Facebook Pages managed by the connected Meta user (id, name, category). The page_id required when creating ads is selected from here. With account_id, this tool also returns which Pages that ad account is actually allowed to advertise for (Meta's own `promote_pages`), as `ad_account_pages` with `assigned_to_ad_account` on every entry. A Page in the flat list does NOT mean the ad account can use it: the user's personal Page role and the ad account's asset assignment are two different things, and Ads Manager shows the former. An empty `ad_account_pages` means Meta could not DISCOVER an assigned Page — it does NOT mean ads cannot be built, and it is NOT a connector fault. Verified live on 2026-09-22: with promote_pages empty, passing page_id explicitly created a WhatsApp messaging ad set without any error. So when `ad_account_pages` is empty, pick the Page from the `pages` list and pass page_id directly to create_meta_adset / create_meta_link_ad FIRST. An empty list here is a discovery gap, not proof of an asset-assignment problem; that is shown only when Meta rejects an explicit page_id. A Page missing here is not an access loss on our side. If the list comes back empty this tool also reports WHY: a missing `pages_show_list` permission looks identical to "no pages" otherwise. Each Page row carries `assigned_to_ad_account`; `ad_account_pages_count` is the corresponding summary, so the same rows are not duplicated outside the response page. Every matching Page is retained: limit controls only this response page (0 = as many as fit), and page_token=next_page_token retrieves the cached remainder without another Meta request or credit.