Ads
listAdAccounts
List Ad Accounts
listAdAccounts: list the Meta ad accounts the caller's Meta Ads connection can reach, each marked sandbox or real, usable or refused, with the refusal reason.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "which ad accounts do I have", and it calls listAdAccounts.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"clientRequestId": "<clientRequestId>",
"dryRun": true
},
"name": "listAdAccounts"
}Arguments
clientRequestIdstringrequiredA stable id you mint for THIS request (e.g. a UUID) and reuse on a retry. A repeat of a succeeded id returns its receipt instead of calling Meta twice.dryRunbooleanrequiredtrue runs the account gate and writes a dry_run receipt without sending anything to Meta. Use it first to preview.
Returns
The registry does not declare a return shape.
Declared limits
clientRequestId: minimum length 8clientRequestId: maximum length 128
Ask for it
The Cloud routes these requests to this verb.
- which ad accounts do I have
- list my Meta ad accounts
- is my sandbox ad account connected
Pair it with
The verbs that finish the job.
Questions
What does listAdAccounts do?
listAdAccounts: list the Meta ad accounts the caller's Meta Ads connection can reach, each marked sandbox or real, usable or refused, with the refusal reason. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use listAdAccounts from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "which ad accounts do I have", and it calls listAdAccounts.
Is listAdAccounts safe to let an AI call?
listAdAccounts is read-only: it changes nothing. It reaches a system outside The Cloud on your behalf.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.