Skip to main content
Glama
Sign In
Pinterest Ads MCP Server

Pinterest Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List hosted tools

list_hosted_tools
Read-onlyIdempotent

Lists hosted Pinterest Ads tools to show what an agent can do after connecting, such as creating campaigns, pulling performance data, or uploading media.

Instructions

List the tools of the hosted Pinterest Ads MCP server by AdKit (https://mcp.adkit.so/pinterest-ads), with one line on what each tool does. Use this to explain what an agent can do with ad accounts after connecting, such as creating campaigns, pulling performance or uploading media. Returns a Markdown table. It does not call those tools; they only run on the hosted server.

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": "list_hosted_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the return format is a Markdown table, and it explicitly states the listed tools are not invoked but only run on the hosted server, which prevents a false assumption of side effects. Missing only detail such as what happens when the hosted server is unreachable.

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?

Three sentences, front-loaded with the purpose and followed by the use case, return format and a caveat. There is minor redundancy between the URL parenthetical and the 'hosted server' phrasing, but no filler.

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?

For a zero-parameter, read-only listing tool with no output schema, the description supplies everything needed: what it lists, the source server, the return format (Markdown table) and the boundary that it does not execute the listed tools. Nothing an agent needs in order to call it correctly is missing.

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 schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline for a parameterless tool 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 ('List the tools of the hosted Pinterest Ads MCP server') and scopes it to the hosted server, which cleanly separates it from sibling tools like list_ad_platforms or get_setup_guide. It also says what each entry contains ('one line on what each tool does').

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 use case: use it to explain what an agent can do with ad accounts after connecting, with concrete examples (creating campaigns, pulling performance, uploading media). It does not name when to prefer an alternative or when not to call it, so it stops short of a 5.

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