Hosted Pinterest Ads MCP server, with each action switched on or off per account.
Scored across 4 tools
The tools have mostly distinct roles: query_data handles reads, execute_action handles writes/actions, query_contexts supplies prerequisite metadata, and prompts_menu browses prompts. The shared workflow language between execute_action and query_data creates slight overlap, but their read-vs-write distinction is clear.
Three tools follow a readable verb_noun convention (execute_action, query_contexts, query_data). prompts_menu is a noun-style outlier, but it remains understandable and the overall set is mostly consistent.
Four tools is a compact but reasonable surface for this workflow-oriented Pinterest Ads server. Each tool serves a clear role, though the set is slightly thin and depends heavily on the context/helper pattern.
The generic query/execute pair, backed by context discovery and action-detail lookup, can cover a broad range of Pinterest Ads reads and writes. There are minor gaps around standalone diagnostics or explicit resource-specific operations, but the dynamic action catalog reduces dead ends.
Execute Pinterest Ads action (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions
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.
Inputs: body (required). Returns: object
Helper for planning InsightfulPipe Pinterest Ads queries and write actions.
Step 1: request='accounts' – Retrieve workspace_id, brand_id, ad_account_id, other source metadata, AND available_actions (all tables/actions you can query or execute).
Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.
Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).
Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.
Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object
Query Pinterest Ads data (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions
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.
Inputs: body (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hosted Pinterest Pages MCP server, with each action switched on or off per account.
Hosted LinkedIn Ads MCP server, with each action switched on or off per account.
Hosted Snapchat Ads MCP server, with each action switched on or off per account.
Hosted Microsoft Ads MCP server, with each action switched on or off per account.
Add one secure layer between your agents and this server.
