Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

Get keyword search volume

pinterest_ads_get_keyword_metrics
Read-onlyIdempotent

Retrieve monthly Pinterest search volume for up to 2,000 keywords in a specified country to size keyword ideas and compare demand.

Instructions

Monthly search volume on Pinterest for keywords in one country (e.g. 'GB', 'US').

Up to 2000 keywords. Aggregated across Pinterest; use it to size keyword ideas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>",
      "country_code": "<country_code>"
    },
    "name": "pinterest_ads_get_keyword_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYes
country_codeYes
ad_account_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world), so the bar is lower. The description adds genuinely useful behavior: monthly granularity, a hard cap of 2000 keywords per call, and that results are aggregated across Pinterest rather than scoped to an ad account.

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?

Two short sentences with the core metric front-loaded and the constraint and usage hint following. No filler, though the parenthetical country examples are largely schema-redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the description covers granularity, limits and aggregation. The only real hole is the unaddressed ad_account_id parameter, which conflicts conceptually with the 'aggregated across Pinterest' framing.

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 carry parameter meaning. It successfully clarifies country_code (single country, examples 'GB'/'US') and the keywords limit, but leaves ad_account_id completely unexplained — and that omission is especially confusing since the description says results are aggregated across all of Pinterest, implying the account id has no effect.

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 names the specific metric (monthly search volume), the platform (Pinterest), the scope (one country) and its intended use (sizing keyword ideas). That distinguishes it from the discovery-oriented sibling suggest_keywords, though it never names that sibling explicitly.

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?

"Use it to size keyword ideas" gives a clear positive cue for when to call it, but there is no explicit contrast with pinterest_ads_suggest_keywords or pinterest_ads_list_keywords, so the agent must infer which keyword tool to reach for in a given situation.

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