Skip to main content
Glama
Sign In
Pinterest Ads MCP Server

Pinterest Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Provides step-by-step instructions to connect a selected AI app to the hosted Pinterest Ads MCP server, including exact menu paths, commands, or config snippets.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted Pinterest Ads MCP server by AdKit at https://mcp.adkit.so/pinterest-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": {
      "app": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the output medium and granularity: Markdown containing the exact menu path, command, or config snippet. It does not discuss per-app variability or fallbacks if an app is unsupported, which keeps it short of a 5.

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 sentences, front-loaded with the purpose, then the usage trigger, then the return format and the sibling pointer. Every sentence carries distinct information and nothing is repeated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description compensates by specifying the return format (Markdown with menu path, command, or config snippet). For a one-enum-parameter read tool with full annotation coverage, an agent has everything needed to select and invoke it correctly.

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 coverage is 100% and the single parameter is an enum with its own description ('The AI app to connect, exactly as listed'), so the schema carries the semantics. The description only adds 'in a specific app', which conveys the one-app-per-call scope but no new format or selection guidance. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieve step-by-step instructions for connecting one AI app to the AdKit-hosted Pinterest Ads MCP server. It also names the sibling it is not (list_hosted_tools) and pins down the artifact returned, so an agent can distinguish it from list_hosted_tools, get_faq, or get_example_prompts without opening any schema.

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?

Gives an explicit trigger condition — 'Use this when the user asks how to install, add or connect AdKit in a specific app' — and routes the adjacent need ('what the hosted server can do once connected') to list_hosted_tools. Both the when and the alternative are stated rather than inferred.

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