Skip to main content
Glama
Pinterest Ads MCP Server

Pinterest Ads MCP Server

Download a finished report

pinterest_ads_download_report
Read-onlyIdempotent

Download a finished Pinterest Ads report and return its rows in memory up to a set limit, including the full row count and whether results were truncated.

Instructions

Download a FINISHED report and return its rows (up to max_rows), held in memory only.

row_count is the full count; truncated says whether rows were cut to max_rows. report_format must match the one the report was requested in.

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": {
      "token": "<token>"
    },
    "name": "pinterest_ads_download_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
max_rowsNo
ad_account_idNo
report_formatNoJSON

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added context is the differentiator: results are held in memory only, and row_count/truncated disclose how truncation to max_rows is signalled. That is useful behavior beyond the structured fields, though it omits what happens on a format mismatch or a non-finished report.

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?

Three short sentences, front-loaded with the download action and scope, then the truncation semantics and format constraint. No redundant restatement of the name or title; every clause conveys information an agent needs.

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 only be described at the level of row_count/truncated, which the description does. The remaining gap is the undocumented token/ad_account_id parameters and the absence of any note on error conditions for a not-yet-finished report.

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% across four parameters, so the description must carry the load. It explains max_rows (via the truncation mechanism) and report_format (must match the original request), but says nothing about token or ad_account_id, leaving half the parameters undocumented anywhere.

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?

Uses a specific verb (Download) and resource (report) and adds a discriminating qualifier: the report must be FINISHED, which separates it from the sibling create_report/get_report/run_report tools by lifecycle stage. It does not name those siblings explicitly, so the disambiguation is implied rather than stated.

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 capitalised FINISHED and the note that report_format must match the requested format imply a pre-condition and a sequencing rule (create/run first, then download). However, there is no explicit when-to-use vs pinterest_ads_get_report guidance and no stated failure behavior if the report is still running.

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