Pinterest Ads MCP Server to Manage Campaigns from Chat

An MCP server turns an ad platform's API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "pause every Pinterest ad group whose CPC is above $2 in the last 14 days" becomes something the assistant can check, propose, and, once you approve, execute. This page covers PaidSync's Pinterest Ads surface in full: the 14 tools, exactly what they do and do not do, how the approval gates work, and how it compares with the Pinterest MCP options on most current lists.

It is written for both audiences. Marketers who want to manage Pinterest campaigns day-to-day from a chat window, and agent builders who want to know exactly what the protocol surface looks like before wiring it into a workflow. Each section is labeled.

What a Pinterest Ads MCP server does (and what PaidSync's does not)

Three things, in practice. It reads, so the assistant can pull spend, CPC, and saves without you exporting from Ads Manager. It manages, so existing campaigns and ad groups can be paused, enabled, re-budgeted, and updated through conversation. And it gates, so nothing the AI proposes runs until a human confirms it.

The honest bit up front: PaidSync's Pinterest tool set is manage-only. It does not create new campaigns, does not create ad groups, does not upload Pins, and does not manage catalog feeds as tools of its own. For those, you use Pinterest Ads Manager. PaidSync's role starts the moment a campaign is live and takes daily management, optimization, and reporting off your plate. This is different from the Google, Meta, LinkedIn, and TikTok surfaces, where PaidSync also builds from scratch; see the capability matrix on the full MCP server page.

All 14 Pinterest Ads tools by category

PaidSync's live server exposes 14 Pinterest tools (server total 430+ across 13 platforms). The table names all of them; the live catalog is also discoverable from any session via paidsync_context with include_tools:['pinterest'].

Three of these carry most of the operational work. update_pinterest_campaign_budget re-paces spend without opening Pinterest Ads Manager, update_pinterest_campaign edits name, status, and campaign-level settings, and update_pinterest_adgroup handles ad-group settings including bidding and targeting fields exposed by the Pinterest Ads API. Combined with get_pinterest_performance and the list_* readers, a Monday-morning pacing and pausing pass runs entirely in chat.

Manage Pinterest Ads from a chat window

The practical shape of a week on PaidSync's Pinterest stack looks like this. Monday morning you ask "what changed in the last 7 days on Pinterest, by campaign, and where is CPC drifting". The assistant pulls it from get_pinterest_performance and answers in plain numbers. You spot two ad groups pacing over budget on stale Pins, ask for a pause on the worst offender and a 30% budget cut on the other, review the drafted changes, and confirm. Later you ask for a status report on live campaigns; the assistant lists them from list_pinterest_campaigns.

Because the same server carries Google Ads (136 tools), Meta Ads (69 tools), LinkedIn (25 tools), TikTok (13 tools), GA4 (28 tools), and GTM (37 tools), the follow-up question "did the Pinterest cut shift volume to Meta shopping and did GA4 see the difference" is answered in the same session, not in another tab. That cross-platform session is the practical difference between a Pinterest connector and a paid-media server.

Trust is procedural, not promissory. Nothing applies without your confirmation, previews show the exact planned change first, and destructive operations require a second explicit confirmation. Sessions can be revoked at any time.

The protocol surface behind the 14 tools

PaidSync is one MCP endpoint covering 13 platforms; details on the MCP server page. To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active account, connected platforms, and the grouped tool catalog (include_tools:['pinterest'] returns the exact Pinterest tool names), and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke all 14 Pinterest tools without a 430-tool schema payload sitting in every conversation.

Safety is enforced server-side. Writes are approval-gated, most mutation tools accept dry_run for a no-op preview, and destructive operations require confirm_destructive. For discovery and verification, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive.

PaidSync vs Zapier MCP vs Composio

Two general-purpose options show up on current Pinterest MCP lists. Zapier MCP surfaces Zapier's Pinterest integration through the MCP protocol; useful if you already automate Pinterest through Zapier, and it inherits Zapier's 9,000+ app ecosystem. Composio's Pinterest connector is a developer toolkit aimed at engineers wiring Pinterest endpoints into custom agents; no approval-gate layer. PaidSync is hosted, ad-operations focused, and manages existing Pinterest campaigns alongside 12 other platforms in one session with approval gates.

What this does not do

Stated plainly, because scoping a tool accurately beats overselling it.

• No new Pinterest campaigns or ad groups. Build them in Pinterest Ads Manager, then hand to PaidSync.
• No Pin uploads. Image and video Pins are created in Pinterest.
• No catalog feed management. Product catalogs are managed in Pinterest today.
• One object per task. Updating 10 ad groups is 10 confirmed tasks.
• No unattended spend. Every write waits for your confirmation.

Roadmap decisions on Pinterest coverage track customer demand. If a capability above is central to your workflow, tell us at the demo booking page.

Pricing

Every plan includes all 13 platforms and there is no per-account or per-platform charge. Every tool call counts as one task. Full detail at paidsync.ai/pricing.

Frequently asked questions