Skip to main content
Glama
Sign In

Pinterest Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Pinterest Ads Data Query

query_data
Read-only

Query Pinterest Ads data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-structured context by making execution contingent on two prior discovery calls and warning not to guess the body shape. It says nothing about result size, pagination, or rate behavior, but for a read-only query that is a modest gap.

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?

Front-loaded with the workflow position and the 'REQUIRED' block, which is the right priority. The 'IMPORTANT: Always call step 2' line largely restates item 2, making it slightly redundant, but the whole description is short and scannable.

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 no explanation, and the description covers the one thing an agent cannot infer: that the body must be derived from actions_details. Given the opaque free-form body, a pointer to the structure source is the reasonable completeness standard here.

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?

There is a single 'body' parameter with 0% schema coverage and additionalProperties=true, so the schema conveys nothing about its shape. The description partially compensates by pointing to actions_details as the authoritative source for the exact body structure, but it offers no field-level semantics of its own.

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 ('Query') and resource ('Pinterest Ads data') and anchors itself as 'Step 3 (FINAL) of workflow', which distinguishes it from the prerequisite query_contexts call. It does not say what kinds of data or entities can be queried, so the actual capability remains opaque until the body is constructed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Unusually explicit sequencing: it names the two required query_contexts calls (request='accounts', request='actions_details'), tells the agent where the inputs come from (available_actions), and warns 'Always call step 2'. It does not clarify when to prefer this over the sibling execute_action, so the write/read routing is only implied by the readOnlyHint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pinterest Ads MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources