Skip to main content
Glama
Sign In

Pinterest Pages MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Pinterest Pages Execute Action

execute_action
Destructive

Execute Pinterest Pages action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, pinterest_user_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 executing.

Rely on info from steps 1-2 to construct the action 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": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=true, so the description is not required to repeat the safety profile. It adds valuable behavioral context by specifying that this is the final workflow step and that the body must be derived from prior query_contexts calls. It does not itself warn about irreversibility or permissions, but the annotations cover the destructive nature.

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?

The description is front-loaded with the final-step role and uses REQUIRED and IMPORTANT markers to surface the critical workflow. It is somewhat repetitive in restating the need to call step 2, and the placeholder action IDs are noisy, but no sentence is fundamentally wasteful.

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?

Given the complex dynamic body, destructive/open-world annotations, and an output schema, the description supplies the essential prerequisite workflow and body-construction guidance an agent needs before calling. It omits explicit consequence details such as irreversibility, but the annotations already carry the destructive signal and an output schema exists.

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?

Schema description coverage is 0% for the single dynamic 'body' object, so the description must compensate. It does so by instructing the agent to call query_contexts with request='actions_details' to obtain the exact body structure and to follow the schema exactly. It does not enumerate body fields, but for a dynamically shaped action body the guidance is meaningfully more than the schema provides.

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 states a specific verb and domain resource: 'Execute Pinterest Pages action (Step 3 (FINAL) of workflow).' It makes the tool's role as the final execution step clear and distinguishes it from the prerequisite query_contexts step. It does not explicitly name all sibling differences, and 'action' remains broad, which keeps it from a 5.

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

Usage Guidelines5/5

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

It gives explicit when-to-use instructions with hard prerequisites: first call query_contexts with request='accounts', then call query_contexts with request='actions_details', and always inspect the exact body structure before executing. This routes the agent unambiguously through the required workflow and names the alternative tool to use beforehand.

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

All Pinterest Pages 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