Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

Get audience insights

pinterest_ads_get_audience_insights
Read-onlyIdempotent

Retrieve 30-day interests and demographics for an ad account's engaged, total, or Pinterest-wide audience to inform targeting and reporting; aggregated data only, not for competitor benchmarking.

Instructions

Interests and demographics of the account's audience over the last 30 days.

audience_insight_type: YOUR_ENGAGED_AUDIENCE (default), YOUR_TOTAL_AUDIENCE or PINTEREST_TOTAL_AUDIENCE. Aggregated data only; don't use it for competitor or platform benchmarking.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pinterest_ads_get_audience_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_account_idNo
audience_insight_typeNoYOUR_ENGAGED_AUDIENCE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds valuable behavioral context by specifying the 30-day window and aggregated-only limitation, but it says little about data freshness, rate limits, or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded, and wastes little space. The parameter explanation is useful, though the formatting is somewhat fragmented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only insights tool, the description covers the key data scope and one parameter well. It is still incomplete because ad_account_id is undocumented and there is no output schema to clarify return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It fully documents the audience_insight_type values and default, which is valuable, but it does not explain ad_account_id or its optionality.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the resource and scope: interests and demographics of the account's audience over the last 30 days. It does not explicitly distinguish this from nearby sibling tools such as pinterest_ads_get_audience or pinterest_ads_estimate_audience_size.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a useful exclusion: aggregated data only, not for competitor or platform benchmarking. However, it does not explain when to choose this over sibling audience or analytics tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools