01 · Records and state owned
Ad accounts, campaigns, ad groups, ads, Pins and creatives, audiences, catalogs and feeds, conversion events, and analytics reports.
Pinterest
Pinterest Ads
Curated major addition platform in visual discovery advertising with material relevance to the Marcom operating stack and a first-party developer surface.
Advertising & media buyingSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve campaign configuration, targeting, delivery state, catalog objects, audience information, and account/campaign/ad analytics.
03 · Actions and write paths
Create and update supported campaigns, ad groups, ads, audiences, catalogs, feeds, and conversion events under approved scopes.
04 · Authentication and permissions
Pinterest OAuth and application scopes apply; the connected business and ad-account permissions define access.
05 · Monitoring, approval, and recovery
Keep spend, targeting, catalog ingestion, creative policy, audience privacy, and launch approvals visible outside Ads Manager.
06 · Gaps and implementation limits
No first-party provider MCP was verified. Endpoint availability, access review, asynchronous analytics, and rate limits vary.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
No first-party provider MCP verified in this snapshotNo first-party provider MCP foundNo first-party provider verified
Role: none_verified
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation2
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Pinterest ships these experiences.
Single-platform patterns
- Visual merchandising and paid-discovery cockpit
- Campaign exception cockpit
- Creative and policy review queue
- Budget pacing workbench
Multi-platform compositions
- Pinterest Ads + CRM or revenue system: campaign exception cockpit
- Pinterest Ads + analytics or warehouse + creative-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
2 recorded sources
APIRepresentative source
https://developers.pinterest.com/docs/api/v5/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party core-access review
HomepageSource inventory
https://business.pinterest.com/advertise/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.