Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

List the Pins on a board

pinterest_ads_list_board_pins
Read-onlyIdempotent

Lists Pins on a Pinterest board, including protected Ad-only Pins boards, so you can select a Pin for an ad.

Instructions

List the Pins on a board, e.g. the protected 'Ad-only Pins' board, to pick one for an ad. Apps registered on or after 14 September 2026 may get HTTP 403 PINNER_DATA_ACCESS_DENIED here until Pinterest approves Pinner data access; don't retry.

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": {
      "board_id": "<board_id>"
    },
    "name": "pinterest_ads_list_board_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYes
max_resultsNo
ad_account_idNo
creative_typesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so credit goes to what the description adds: the specific 403 PINNER_DATA_ACCESS_DENIED failure mode tied to app registration date on or after 14 September 2026, and the explicit 'don't retry' instruction. That is real, actionable operational context beyond the annotations; only pagination/result-size behavior is left unstated.

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

Conciseness5/5

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

Two tight sentences with no waste: the core action and use case come first, then the failure-mode caveat. Every clause carries information the agent needs.

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?

An output schema exists, so return values needn't be explained, and the access-denied caveat covers the biggest operational risk. However, with four undocumented parameters and no guidance on result sizing or pagination, an agent calling this with creative_types or ad_account_id is guessing.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description compensates only marginally — 'on a board' hints that board_id identifies the board, but nothing explains the format of board_id, what max_results controls, when ad_account_id is required, or what creative_types filters on. For a 0%-coverage schema, this leaves three parameters effectively opaque.

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?

States a specific verb and resource ('List the Pins on a board') plus a concrete use case ('to pick one for an ad'), and the mention of the protected 'Ad-only Pins' board scopes it further. It stops short of naming how it differs from the sibling pinterest_ads_list_pins, which an agent must infer from the 'on a board' phrasing.

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?

The intended use ('pick one for an ad') implies when to reach for it, and the 'don't retry' instruction gives a clear behavioral rule on failure. There is no explicit statement of when to use pinterest_ads_list_pins or pinterest_ads_get_pin instead, so the alternative routing is left implicit.

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