Pinterest Ads MCP Server
Related Servers
Alternatives to Pinterest Ads MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to report on and manage Ads Manager campaigns, creative sets, assets, and MAX ad units, waterfalls, experiments, and revenue data, with dry-run, confirmation, and audit-log safeguards for writes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables reporting on and managing Sponsored Products, Sponsored Brands, and Sponsored Display campaigns, keywords, targets, bids, budgets, portfolios, and budget rules through MCP clients, with dry-run, confirmation guards, read-only mode, and an audit log for safer write operations.MIT
- FlicenseNot gradedqualityCmaintenanceEnables management of Google Ads accounts via MCP, providing read and write tools for campaigns, ad groups, keywords, assets, and more, with support for reporting and mutations.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to report on TikTok ad accounts and build or change campaigns, ad groups, ads (including Upgraded Smart+), creatives, audiences, pixels, catalogs and reports through the TikTok Marketing API. Writes are protected by dry-run mode, confirm words, spend guards, before-snapshots, an audit log and read-only mode.MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to read Snapchat Ads campaigns and performance and to prepare preview-first changes for selected ad accounts, with opt-in write tools and explicit confirmation before applying updates.21613 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients to inspect ad account structure, campaign performance, demographic breakdowns, and revenue attribution, and to prepare opt-in, preview-first draft campaigns, ads, and media uploads for explicitly selected accounts.18304 npmApache 2.0
TDQS
Scored across 81 tools
The bulk of the surface is cleanly partitioned by resource (campaigns, ad_groups, ads, keywords, audiences, catalogs, product_groups) with matching list/create/update/archive verbs, so misselection is unlikely. The main overlaps are the metrics path (get_analytics vs. the create/get/download/run_report family) and run_report as a wrapper around create_report, which the descriptions do address but still leave two ways to accomplish the same read.
Nearly all tools follow a consistent pinterest_ads_ verb_noun pattern (list_, get_, create_, update_, archive_, delete_, set_, adjust_, estimate_, suggest_). Minor deviations exist in pinterest_ads_request / pinterest_ads_read_request (no verb_noun) and the bulk/batch utilities (bulk_upsert, bulk_export, batch_catalog_items), but overall it is predictable.
81 tools is far past the point where an agent can scan the set comfortably, and several tools are thin wrappers or conveniences (run_report vs create_report, read_request vs request). The domain is genuinely broad, but the surface is heavy enough that batching/consolidation would materially help.
CRUD/lifecycle coverage is strong across campaigns, ad groups, ads, keywords, audiences, customer lists, catalogs and product groups, plus reporting and escape-hatch raw endpoints. Minor gaps remain, e.g. targeting templates are list-only and conversion tags are read-only, but these are workable via the generic request tools.