Skip to main content
Glama
Sign In
Pinterest Ads MCP Server

Pinterest Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get example prompts

get_example_prompts
Read-onlyIdempotent

Get example prompts for reporting, optimizing, and launching Pinterest Ads campaigns when users ask what to try first. Returns a Markdown list.

Instructions

Get example prompts that work with the hosted Pinterest Ads MCP server by AdKit, such as reporting, optimizing and launching campaigns. Use this when the user asks what to try first or what to ask the agent. Returns a Markdown list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_example_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the return format ('Returns a Markdown list'), which is genuinely useful given there is no output schema, but nothing about content volume, variability, or freshness.

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 tight sentences with no filler: purpose first, then the usage condition, then the return shape. Nothing is redundant and the ordering is front-loaded with the most decision-relevant information.

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?

For a trivial zero-parameter, side-effect-free tool with no output schema, the description covers purpose, trigger, and return format adequately. A minor gap is that 'Pinterest Ads by AdKit' suggests a platform scoping that other siblings (list_ad_platforms) might indicate is not universal.

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?

The tool takes zero parameters and the description correctly implies a parameterless call. Baseline 4 applies since there is no parameter surface to explain.

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 example prompts that work with the hosted Pinterest Ads MCP server by AdKit') and scopes the content with concrete examples (reporting, optimizing, launching campaigns). It is clearly distinguishable from get_faq and get_setup_guide by content type, though it never explicitly contrasts itself with those siblings.

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?

Gives an explicit activation trigger: 'Use this when the user asks what to try first or what to ask the agent.' That is a clear context for use, but there is no guidance on when NOT to use it (e.g., setup questions belong to get_setup_guide).

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