Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

pinterest_search

Search Pinterest by query to find matching pins and content, with optional trimmed responses and cursor-based pagination.

Instructions

pinterest: Search. GET /v1/pinterest/search. Search Pinterest Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "query": "<query>"
    },
    "name": "pinterest_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet true for a trimmed response.
queryYesSearch query
cursorNoCursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real behavioral value by spelling out the credit model: 1 credit on success, no charge for errors, blocked, timed-out, invalid, or cache-hit requests. However, it omits other behavior an agent needs, such as authentication requirements, rate limits, pagination behavior via the cursor, and what kind of entities (pins, boards, users) are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement is front-loaded, which is good, but the bulk of the text is a verbose, repetitive billing paragraph ('costs nothing... charged only where that operation's published cost says so') that could be condensed to one clause. The sentence 'Search Pinterest Costs 1 credit when it succeeds.' is also missing punctuation and reads as a run-on.

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

Completeness2/5

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

For a search tool with no annotations and no output schema, the description should say what results come back and how to page through them. It covers billing thoroughly but leaves result shape, pagination semantics, and any auth or rate-limit constraints entirely undocumented, which is a significant gap for this complexity.

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 description coverage is 100% with all three parameters (query, trim, cursor) documented in the schema, so the schema does the heavy lifting. The description adds no meaning beyond the schema — it never mentions the cursor's role in paging or what a trimmed response contains — so the baseline of 3 applies.

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 names a concrete verb and resource ('Search Pinterest') and gives the underlying endpoint 'GET /v1/pinterest/search', so an agent knows exactly what the tool does. It does not distinguish itself from the many sibling search tools (reddit_search, youtube_search, tiktok_search_keyword), leaving the agent to infer that this one targets Pinterest only from the name.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only contextual information provided is a billing policy, which tells the agent about cost but not about selection between tools.

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