Get performance cube
The window grouped and crossed on campaign, ad set, country, ad, upload or Values.
rows takes one axis or two, comma-separated (nested); column crosses them. An ad with two Values on an axis counts under each, so the total is never a sum of rows.
Requires a key with read scope or higher.
MCP: meta_get_performance_cube.
bearerAuthAuthorizationBearer <token>An API key from Settings → API keys, sent as Authorization: Bearer rsk_….
Authorization has two independent axes.
The scope is ranked — a key satisfies any requirement at or below its own tier:
read— every GET.write— launch ads PAUSED, sync, pull history, edit thresholds, Values, briefs, tests, swipes and research.admin— everythingwritecan. No operation requires more thanwritetoday.
There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.
The approval grant (can_approve) is a separate boolean, not a rung. Changing spend on Meta — activating a launch, pausing or resuming ads, retargeting an ad set, or rebuilding a launch's live creative — needs write and the grant. Keeping them on separate axes is what makes the review gate a control rather than a convention: a key that may propose is not automatically a key that may approve its own proposal.
A key reaches the one workspace — one Meta ad account — it was minted in, and stops working when the operator who minted it leaves the workspace. The same key authenticates the MCP endpoint (/api/mcp) for a headless agent, with the same scope and grant.
rows*stringComma-separated, or the parameter repeated.
column?string"campaign""adset""country""ad""creative""concept""angle""persona""awareness""offer""offer_type""pain""season""asset_type""format""hook""headline_tactic""talent""visual"campaign_ids?stringOnly these campaigns.
limit?integerTop rows by spend.
1 <= value <= 20050period?stringReporting window. 7d/14d/30d are the last N complete days, ending yesterday (as in Ads Manager); weeks are Monday-based, this_week runs to today. UTC.
"7d""7d""14d""30d""this_week""last_week"since?stringCustom window start, YYYY-MM-DD, UTC. Overrides period. The result's coverage says what the warehouse holds.
until?stringCustom window end, YYYY-MM-DD, inclusive. Default today.
Success. The body is the tool's own result — the same payload the MCP tool returns.
application/json- response
curl -X GET 'https://winandscale.com/api/v1/performance-cube?rows=string'{}