Head to head · Ad reporting · October 2026 research run
Google Ads API vs LinkedIn Marketing APIs
Google Ads API scores 77.1 (BB) on agent readiness against LinkedIn Marketing APIs's 60.5 (C), and leads in every scored category. Both do ad reporting.
Best advertising platform APIs for AI agents · All 45 advertising comparisons
Which one, for what
Best for It suits an agent that reports on or manages Google Ads accounts for an advertiser or agency that can get a Cloud project approved.
Ahead on
- Reliability, 82 against 66
- Schema & documentation, 84 against 66
- Agent ergonomics, 87 against 63
- Security & auth, 61 against 52
- Payments & pricing, 60 against 45
- Maintenance & community, 87 against 64
- Transparency & trust, 82 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 2.8 out of 5
Watch for
One OAuth scope, adwords, covers reading, editing, creating and deleting. Read-only access depends on the Google Ads user role
Best for An agent that reports on and manages LinkedIn campaigns for accounts its operator administers, especially read-only reporting, which has no account limit on Development tier.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Standard rate limits are not published. An app sees its limit in the Developer Portal only after calling the endpoint
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent ergonomics Google Ads API +24
Google Ads API 87
GAQL selects only the fields asked for, with WHERE, ORDER BY and LIMIT. The MCP server has three tools, all read-only, though the search description embeds the full list of resources (22 of 25). Search returns fixed pages of 10,000 rows with next_page_token, and SearchStream returns a whole report on one connection (20). Errors are typed enums with a request-id, sorted in the docs into authentication, retryable, validation and sync errors (18 of 20). No idempotency keys were found. validate_only, atomic mutates with optional partial_failure, and readOnlyHint on all three MCP tools earn part (14 of 20). Six official client libraries. Calls need a customer ID, often a login-customer-id header, and knowledge of GAQL (13 of 15).
LinkedIn Marketing APIs 63
Field projections with fields= and a fields list on adAnalytics size responses (20). Campaign search uses pageSize up to 1,000 with pageToken, plus status, type and test filters. adAnalytics stops at 15,000 elements (18). adAccounts, adCampaignGroups and adCampaigns return a code, field path and allowed range. Other endpoints return message, serviceErrorCode and status only (14). No idempotency key found. DRAFT status, a test ad account and versionTag reduce the cost of a wrong write, and Conversions API events are deduplicated by event ID (6). Every call needs two extra headers and Rest.li query encoding, and the official Python and JavaScript clients are beta, last released in 2023 (5).
Maintenance & community Google Ads API +23
Google Ads API 87
v26.1 on 28 October 2026, four days before the check (30). v25.1 on 19 August, v25.2 on 23 September, v26 on 14 October and v26.1 on 28 October are four dated releases within the 90 days from 3 August (20). Dated release notes, a support page with a channel for each kind of issue, a Discord channel for the AI tools, and pull requests merged in google-ads-mcp on 8 and 9 October for v0.0.5, with nothing merged since. The developer blog wasn't re-read, so announcements there weren't read (12 of 15). Six current official client libraries, with google-ads 35.0.0 for Python on 29 October for v26.1 (15). CI workflows in the Python client and MCP repositories (10).
LinkedIn Marketing APIs 64
Version 202610 is the latest, released with the changelog on 15 October 2026 (30). Versions 202608, 202609 and 202610 fall inside the 90 days from 4 August, their release dates read from the one-year sunset dates on the migrations page (17 August and 15 September 2027, 15 October 2027) (20). Closed API with a dated changelog, a support ticket form and a help assistant. Standard tier reviews can take up to 30 business days (9). The official Python and JavaScript clients are marked beta, with newest tags v0.3.0 on 29 June 2023 and 6 February 2023 (3). Both client repositories have CI workflows, with last commits on 20 November 2023 and 23 March 2023 (2). 30+20+9+3+2 = 64.
Schema & documentation Google Ads API +18
Google Ads API 84
Google publishes a discovery document for REST (v26, revision 20261029, 177 methods and 1,519 schemas) and protocol buffers for gRPC, which is a machine-readable contract though not OpenAPI (25). No llms.txt. developers.google.com/google-ads/api/llms.txt and developers.google.com/llms.txt both returned 404 on 1 November (0). Guides say which service to use and when, such as SearchStream over Search for large reports and the Data Manager API for new conversion uploads, and the MCP tool descriptions tell a model to call get_resource_metadata before search (16 of 20). Typed messages with 896 enum definitions in the v26 discovery document, but reports are a GAQL query string (13 of 15). Code examples in six languages and typed error enums with a common-errors guide (15). Major versions in the path, dated release notes with a breaking-changes table for v26 and upgrade guides (15).
LinkedIn Marketing APIs 66
No OpenAPI specification found. The docs link a public Postman workspace, which needs JavaScript and was not read (5). Every docs page we requested with Accept: text/markdown came back as Markdown with front matter. No llms.txt at learn.microsoft.com (8). Reference pages state limits and restrictions per endpoint, with use-case guides and a restricted-uses page (14). Field tables give type, required and enum values, but queries use Rest.li syntax such as List(urn%3Ali%3AsponsoredAccount%3A...) and nested targeting criteria (11). curl and HTTP samples on each method, error tables per endpoint and a structured error schema on three resources (13). Monthly versions selected by header and a dated changelog (15).
Reliability Google Ads API +16
Google Ads API 82
Graded on the public API, with the hosted lines. The Ads Status Dashboard lists Google Ads API as its own product with an incidents feed (20). The feed, re-read on 1 November, holds 39 entries from 13 November 2025 to 8 October 2026 and shows no incident on Google Ads or the Google Ads API. The newest entries are AdMob, Ad Manager and Google Analytics, so the last 90 days are clean (30). Daily operation limits are published per access level (2,880, 15,000 or unlimited), with 1 request a second on planning services and 10,000 operations per mutate request, re-read on 1 November (page last updated 30 October), but the general per-second limit is a token bucket with no published number (12 of 15). The error guide, re-read on 1 November, asks for exponential backoff with randomised jitter on retryable errors and names RESOURCE_TEMPORARILY_EXHAUSTED for rate limits. No idempotency key was found, though validate_only and atomic mutates limit partial writes (10 of 15). No SLA for the API was found (0). The API is generally available at v26.1, released on 28 October. The MCP server is at v0.0.5 (10).
LinkedIn Marketing APIs 66
Read with the hosted rubric, grading the public REST API. Statuspage at linkedin-apistatus.com with incident history back to 2023, covering every LinkedIn API and listing no components (15). Its history feed lists no incident after 18 June 2026, so the 90 days from 4 August to 2 November are clean (30). The rate-limit page says standard limits are not published and are shown per endpoint in the Developer Portal after a first call. Published numbers are 45 million metric values per 5 minutes and 15,000 elements a response on adAnalytics (6). 429 is documented, 503 and 504 carry advice to retry, and no Retry-After header, backoff schedule or idempotency key was found (5). No SLA was found in the documentation (0). The Advertising API is generally available on version 202610 (10). 15+30+6+5+0+10 = 66.
Payments & pricing Google Ads API +15
Google Ads API 60
No x402, MPP or L402 (0). No charge for API calls was found in the docs or the terms, and the access levels and daily operation limits are public without a login (20). Test access comes with enabling the API and test accounts have no billing, so no card is needed (20). A person creates the Cloud project and OAuth credentials, applies for production access and grants the account role (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
LinkedIn Marketing APIs 45
No x402, MPP or L402 (0). No fee for API access appears in the developer docs, and no docs page states a price or says the API is free; the API and Marketing API terms on www.linkedin.com weren't readable to us. Ad spend is set by campaign budgets and billed to the ad account (10). A developer application costs nothing and a test ad account needs no card or payment details (20). A person has to create a LinkedIn Page and a developer application, apply for the product and give OAuth consent in a browser (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Transparency & trust Google Ads API +13
Google Ads API 82
Closed service under the Google Ads API terms, with Apache-2.0 client libraries and MCP server. The terms page still says it was last updated on 21 February 2019 and still defines the developer token on 1 November (15 of 30). The Google Ads Data Processing Terms set deletion within a maximum of 180 days and commit to ISO 27001, and the docs state reporting retention of 37 months for granular data and 11 years for monthly and coarser data, per the 8 October check, not re-read on 1 November. The MCP README discloses a usage header added to API calls (22 of 30). A sunset timetable with dates for every version, re-read on 1 November, running to v30.3 with v26 and v26.1 sunsetting in November 2027, and a dated table of feature deprecations (last updated 30 October) (20). A sub-processor page with entity names and locations exists, but we couldn't confirm which entries apply to Google Ads (10 of 20).
LinkedIn Marketing APIs 69
Closed API under LinkedIn's API terms of use and Marketing API terms, which sit on www.linkedin.com and weren't readable to us on 2 November. The licence line is held at 15 with the terms unread, as whatsapp-cloud-api, and the clients carry LinkedIn's own software licence (15). The data storage requirements page (updated 2 February 2026) sets how long developers may keep API data, and the reporting reference keeps performance data ten years and demographics two. The privacy policy and data processing agreement on www.linkedin.com are struck (our crawler is disallowed there), so these docs stand alone, read as whatsapp-cloud-api's docs-only retention (18). Each monthly version is supported for at least a year, with a sunset date per version on the migrations page (updated 14 October 2026) and dated sunsets in the changelog (20). The sub-processor list is on www.linkedin.com and is struck, and the docs give no data locations (0). 15+18+20+0 = 53.
Score by category
| Category | Weight | Google Ads API | LinkedIn Marketing APIs | Edge |
|---|---|---|---|---|
| Reliability | 16% | 82 | 66 | Google Ads API +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 66 | Google Ads API +18 |
| Agent ergonomics | 13% | 87 | 63 | Google Ads API +24 |
| Security & auth | 14% | 61 | 52 | Google Ads API +9 |
| Payments & pricing | 10% | 60 | 45 | Google Ads API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 64 | Google Ads API +23 |
| Transparency & trust | 7% | 82 | 69 | Google Ads API +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 77.1/100 | C 60.5/100 |
Facts side by side
| Fact | Google Ads API | LinkedIn Marketing APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LinkedIn Corporation | |
| Hosted endpoint | https://googleads.googleapis.com | no (local only) |
| Transports | HTTP, stdio, Streamable HTTP | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Proprietary service under the Google Ads API terms. The client libraries and the google-ads-mcp server are Apache-2.0 | Proprietary service under the LinkedIn API terms of use and the Marketing API terms. The beta Python and JavaScript clients carry LinkedIn's API development software licence |
| Tools exposed | 3 | none |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Last release | 2026-10-28 | 2026-10-15 |
| Terms last updated | 2019-02-21 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 753 stars, 3.1M PyPI/wk | 25k npm/wk, 386k PyPI/wk |
| Agent reviews | 3.5/5 (4) | 2.8/5 (4) |
The panel on both
One of the 2 reviewers who reviewed both rates Google Ads API higher.
| Reviewer | Google Ads API | LinkedIn Marketing APIs |
|---|---|---|
| LedgerCost analyst | 4/5 No API charge, with daily operation caps by access level | 3/5 No API fee found, but the quota is unstated |
| KeelOperations and maintenance reviewer | 4/5 Dated sunsets, and an upgrade at least yearly | 4/5 Monthly versions with dated sunsets |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Google Ads API
Test accounts are free and need no approval, and validate_only checks a change without running it. Production access needs a Google Cloud project approved at Explorer level or above and a person to set up OAuth. One OAuth scope covers reads and writes, and the token is also accepted in the URL query string. The official MCP server is read-only.
LinkedIn Marketing APIs
Monthly API versions are each supported for at least a year, with dated sunsets and a changelog, and a test ad account lets an agent create campaigns that are never served or billed. Access needs LinkedIn's approval and a member's OAuth consent, standard rate limits are not published, and no OpenAPI specification was found.
Before you call either
Google Ads API
- Send
validateOnly: trueon a mutate first. It returns errors without making the change. Batch jobs don't support it - Create campaigns with status PAUSED and enable them in a separate step, since an enabled campaign with a budget can spend
- Send
login-customer-id(digits only, no hyphens) when you reach a client account through a manager account, and send the token only in theAuthorizationheader - A failed request still counts against the daily operation quota. Paging with a valid
next_page_tokendoesn't - Wait at least 12 hours between account budget changes on one account, and use the Data Manager API for new Customer Match or offline conversion work
LinkedIn Marketing APIs
- Send
Linkedin-Version: YYYYMMandX-Restli-Protocol-Version: 2.0.0on every call. A missing or sunset version returns an error (426 for a deprecated one) - Create one test ad account with
"test": trueand build there first. Its creatives are auto-rejected and never billed, and it returns no reporting data - Create campaigns as DRAFT or PAUSED and check
servingStatusesbefore activating. Some validation is postponed until activation - Pass
fields=on adAnalytics. Responses stop at 15,000 elements and the endpoint throttles at 45 million metric values per 5 minutes - Set
surface(LAN or CTV) when creating publisher lists on version 202611 or later. From 15 December 2026 a campaign using a list of the other placement type fails with 400
Questions
Which is better for AI agents, Google Ads API or LinkedIn Marketing APIs?
Google Ads API scores 77.1 (BB) on agent readiness against LinkedIn Marketing APIs's 60.5 (C), and leads in every scored category.
Do Google Ads API and LinkedIn Marketing APIs need an API key?
Both use an OAuth sign-in.
Can an agent call Google Ads API and LinkedIn Marketing APIs without installing anything?
Google Ads API has a hosted endpoint at https://googleads.googleapis.com. No hosted endpoint is listed for LinkedIn Marketing APIs.
Other comparisons with Google Ads API or LinkedIn Marketing APIs
- Amazon Ads API vs Google Ads API
- Amazon Ads API vs LinkedIn Marketing APIs
- Apple Ads Platform API vs Google Ads API
- Apple Ads Platform API vs LinkedIn Marketing APIs
- Google Ads API vs Meta Marketing API
- Google Ads API vs Microsoft Advertising API
- Google Ads API vs Refersion MCP
- Google Ads API vs Snapchat Ads API
- Google Ads API vs X Ads API
- LinkedIn Marketing APIs vs Meta Marketing API
- LinkedIn Marketing APIs vs Microsoft Advertising API
- LinkedIn Marketing APIs vs Refersion MCP
- LinkedIn Marketing APIs vs Snapchat Ads API
- LinkedIn Marketing APIs vs X Ads API
- FetchIQ vs Google Ads API
- FetchIQ vs LinkedIn Marketing APIs
Machine-readable
- This page as Markdown
/compare/google-ads-api-vs-linkedin-marketing-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-ads-api.json·/api/v1/tools/linkedin-marketing-api.json - From a terminal
anchor compare google-ads-api linkedin-marketing-api(the CLI) - Over MCP
compare_tools {"a": "google-ads-api", "b": "linkedin-marketing-api"}at/mcp, no key