Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

Check the token and list ad accounts

pinterest_ads_health_check
Read-onlyIdempotent

Verify Pinterest Ads API setup: refresh the access token, read the signed-in account, list usable ad accounts, and report granted scopes and rate-limit headers.

Instructions

Check the setup: refresh the access token, read the signed-in account, then list the ad accounts it can use. Also reports granted scopes and the rate-limit headers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds real value by disclosing what the call returns beyond a boolean: granted scopes and rate-limit headers. It does not say what happens if the token is expired or invalid (error vs. refresh), which is the main behavioral unknown for a health check, and 'refresh the access token' sits slightly uneasily with readOnlyHint even though it is defensible as an auth handshake rather than a data write.

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, front-loaded with the 'check the setup' framing and then the concrete steps. No filler. The secondary sentence about scopes and headers is important content rather than padding, though it could have been folded into a single list for faster scanning.

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 explained, and with no parameters the call surface is trivial. The description covers the sequence of actions and the diagnostic outputs, which is enough to invoke the tool correctly. The remaining gap is routing: nothing tells an agent when to prefer this over the dedicated account-listing and user-account tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to add; the schema is empty and fully described. Baseline for a zero-parameter tool applies, and nothing in the description misleads about inputs.

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 specific verbs and resources: refresh the access token, read the signed-in account, list the ad accounts it can use, and report scopes and rate-limit headers. That is far more informative than the title. However, it never distinguishes this tool from its close siblings pinterest_ads_list_ad_accounts and pinterest_ads_get_user_account, which an agent could easily pick instead.

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?

'Check the setup' implies a first-step diagnostic used before other calls, but the description never states that condition explicitly, gives no exclusions, and does not mention the two sibling tools that overlap with its listing behavior. Usage is inferable but not spelled out.

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