Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

Get minimum bids

pinterest_ads_get_bid_floors
Read-onlyIdempotent

Retrieve the minimum bids Pinterest accepts for ad groups by objective, creative type, country, and currency. Read-only; changes nothing.

Instructions

Get the minimum bids Pinterest accepts for ad groups. Changes nothing.

bid_floor_specs: e.g. [{"billable_event": "CLICKTHROUGH", "objective_type": "CONSIDERATION", "creative_type": "REGULAR", "countries": ["GB"], "currency": "GBP"}]. targeting_spec is optional, as in ad group create. Values are micro-units (1.00 = 1000000).

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": {
      "bid_floor_specs": "<bid_floor_specs>"
    },
    "name": "pinterest_ads_get_bid_floors"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_account_idNo
targeting_specNo
bid_floor_specsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so 'Changes nothing' is largely redundant. The description does add genuine behavioral context: results are in micro-units (1.00 = 1000000) and targeting_spec follows the same shape as ad-group create, which matters for interpreting and constructing calls.

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?

Purpose is front-loaded in one sentence, followed by a short param note and example. The example earns its place, though the two-sentence split around the example is slightly awkward rather than maximally tight.

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-value explanation is not required, and the key param is illustrated. Still missing is any treatment of ad_account_id and any explicit routing relative to adjust_ad_group_bids, which an agent needs to sequence bid-floor lookup with bid changes.

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 the load. It gives a concrete example object for the required bid_floor_specs and explains the micro-unit convention, but says nothing about ad_account_id and only one clause for targeting_spec, so the compensation is partial.

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 ('Get the minimum bids Pinterest accepts for ad groups') and adds a scope note ('Changes nothing') that separates it from the bid-mutating siblings like adjust_ad_group_bids. It does not name a sibling explicitly, so it stops short of the top mark.

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?

'Changes nothing' implies this is the read-only way to learn the accepted floor before setting bids, and it notes targeting_spec is 'optional, as in ad group create'. But there is no explicit when-to-use/when-not guidance or named alternative, leaving the agent to infer the workflow.

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