Skip to content
Get MCP AdsGet MCP Ads, home

Rate limits

Get MCP Ads does not cap your calls. Each advertising platform applies its own quotas.

Get MCP Ads does not limit how many calls you make, on any plan and any source. Exports, alerts and agents run as often as they need. Usage is counted per hour so you can see it on the Usage page, and never refused.

Internal admin spend collection uses a separate 120-unit hourly budget per organisation and source. It does not count in your usage or appear as tool activity.

Each advertising platform still applies its own quotas. When a platform throttles a request, the tool returns the platform's own message, and the next call can be made once the platform's window has passed.

Each platform's own quotasLink to this section

AdjustLink to this section

Adjust Report Service permits 50 requests per second per source IP, with a burst allowance of 100. Shared proxies share this provider limit.

Going past it: HTTP 429 responses; respect Retry-After and retry with backoff.

Amazon AdsLink to this section

Amazon applies per-endpoint and application throttling to the Amazon Ads API, without a single published quota.

Going past it: HTTP 429 responses; respect Retry-After.

Apple AdsLink to this section

Apple does not publish a fixed quota for the Apple Ads API and may throttle requests.

Going past it: HTTP 429 responses until Apple lifts the throttle.

LinkedIn AdsLink to this section

LinkedIn applies daily application and member limits per endpoint, shown in its developer portal.

Going past it: HTTP 429 responses until the daily window resets.

Reddit AdsLink to this section

Reddit applies endpoint-specific quotas to the Ads API and returns Retry-After when throttling.

Going past it: HTTP 429 responses; respect Retry-After.

Microsoft AdvertisingLink to this section

Microsoft Advertising applies per-user and per-account call limits to its API.

Going past it: Error 117 (call rate exceeded) until the window resets.

Snapchat AdsLink to this section

Snap averages 20 requests per second per app and 10 requests per second per access token.

Going past it: HTTP 429 responses until the window resets.

X AdsLink to this section

X applies endpoint, user and account limits to the X Ads API, published per endpoint.

Going past it: HTTP 429 responses until the endpoint window resets.

RTB HouseLink to this section

RTB House does not publish a fixed quota and may throttle API requests.

Going past it: HTTP 429 responses until RTB House lifts the throttle.

Meta AdsLink to this section

300 + 40 x active ads per ad account per hour for management calls, and 600 + 400 x active ads for insights, on the Development tier; higher on Standard access. Both are rolling one hour windows.

Going past it: Error 80000, 80003, 80004 or 80014, and the ad account is blocked until the window rolls.

Pinterest AdsLink to this section

Trial access allows 1,000 requests per day for the whole application. Standard access raises this to 100 requests per second per user, with 1,000 per minute on ads reads and 300 per minute on ads analytics.

Going past it: Requests are throttled for the rest of the day.

15,000 API operations per day per developer token on Basic access, shared by every customer of this application. Keyword planning is additionally capped at 1 request per second per customer.

Going past it: RESOURCE_EXHAUSTED, for every customer at once, until the day rolls over.

TikTok AdsLink to this section

10 queries per second, 600 per minute and 864,000 per day per developer app on the Basic level, shared by every customer of this application.

Going past it: Code 40100. A per-minute breach suspends calls for five minutes, a per-day breach until 00:00 UTC.

Search ConsoleLink to this section

1,200 queries per minute per site and per user for Search Analytics. URL Inspection is capped at 600 per minute and 2,000 per day per site.

Going past it: A quotaExceeded error until the window rolls.

Google Analytics 4Link to this section

40,000 core tokens per property per hour, 14,000 per project per property per hour, and 10 concurrent requests per property. Ten server errors per hour on a project and property pair block every request to that property.

Going past it: Quota exhausted, and on the error quota, a full block on the property.

How usage is countedLink to this section

A tool call is almost never one request. Clients paginate, cross several endpoints, and a health check makes a handful by design. So the Usage page counts each call as an estimated number of units rather than one: a report counts more than a list. Nothing is refused on this count.

Kind of toolCounted as
list_accounts, *_list_*1 estimated unit
Most reads and writes2 estimated units
Health checks4 estimated units
Reports and insights5 estimated units
Detectors and monitors, which read a lot to answer once6 estimated units

When a platform throttlesLink to this section

  • The tool returns the platform's own message and code, unchanged.
  • Nothing queues. The call returns at once, so the person using it is never left waiting on a held request.
  • Retry once the platform's window has passed: the sections above say how long each platform's window is.
Esc

Type to search