MCP tool · Account
list_ad_accounts
The ad accounts connected to Apogee.
What it does
List the ad accounts connected to Apogee.
Parameters
-
platformstring optionalAd platform, default meta
-
searchstring optionalFilter on the name
Example
Your assistant calls it for you when you ask in your own words. What it sends (MCP tools/call, JSON-RPC 2.0):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_ad_accounts",
"arguments": {
"platform": "meta",
"search": "spring"
}
}
}The same call over HTTP with an API key, for an MCP client of your own (an assistant that signs in sends its OAuth token instead):
curl -X POST https://app.apogee.ad/mcp \
-H "Authorization: Bearer $APOGEE_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_ad_accounts","arguments":{"platform":"meta","search":"spring"}}}'Access and cost
| Plans | Pro and Scale. |
|---|---|
| Scope | read: a connection or an API key without it does not see this tool (scopes). |
| Effect | Reads only: nothing is changed, in Apogee or on the ad account. |
| Credits | Free up to the daily free reads (5,000 a day on Pro, 10,000 on Scale), then 1 credit per read. A call that fails costs nothing (credits). |
| Rate limit | 600 MCP requests per 15 minutes on Pro, 1,200 on Scale (rate limits). |
| Daily cap | Counts 1 unit toward the 2,000 units one API key or assistant connection can use in 24 hours. |
In the REST API
The same thing for your own code, with an API key:
- List ad accounts:
GET /ad-accounts
Related tools
Account: Who is connected, and the ad accounts to work on.
whoami: The Apogee account this connection acts as, the credential used (an assistant's connection or an API key) and its scopes.