Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

List ad accounts

pinterest_ads_list_ad_accounts
Read-onlyIdempotent

Lists ad accounts available to a Pinterest Ads token, including owned and business-shared accounts, with each account's ID, name, currency, country, owner, and user permissions.

Instructions

List the ad accounts this token can use: owned ones and, by default, ones shared through business access (agency and partner access). Each has id, name, currency, country, owner and the user's permissions on it.

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_list_ad_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNo
include_shared_accountsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds the meaningful nuance that shared/agency accounts are included by default and lists the fields returned, but omits pagination behavior and any cap on results, which matters for a list endpoint with a 200 default.

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 compact sentences, front-loaded with the action and scope, with zero filler. The returned-field list is the only borderline element and is short enough to earn its place.

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?

A simple two-parameter read tool with annotations covering safety and an output schema covering return shape; the description supplies scope and sharing semantics on top of that. The only real gap is pagination/result-cap behavior for max_results, which is minor for this complexity level.

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 partially does: 'by default, ones shared through business access' explains what include_shared_accounts toggles and its default. The max_results parameter is never mentioned, leaving page size and truncation behavior undocumented in both schema and description.

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

Purpose5/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 ad accounts') plus the precise scope: accounts usable by this token, split into owned and business-shared. This clearly separates it from the singular sibling pinterest_ads_get_ad_account without the agent needing to open either schema.

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 phrase 'by default, ones shared through business access (agency and partner access)' implies when shared accounts appear, which is useful. However, there is no explicit guidance on when to call this versus get_ad_account, list_businesses, or list_business_assets, and no stated exclusions or preconditions.

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