Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

pinterest_board

Retrieve pins from a Pinterest board by URL, with optional trimmed responses that retain save counts and keyword labels and cursor-based pagination.

Instructions

pinterest: Board. GET /v1/pinterest/board. Get pins from a Pinterest board. With trim=true, native save counts and keyword labels are retained when available. 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": {
      "url": "<url>"
    },
    "name": "pinterest_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the board to get
trimNoSet true for a trimmed response.
cursorNoThe cursor to get the next page of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the load and does so fairly well: it discloses the credit model (1 credit on success, free for errors/blocked/timeouts/invalid requests/cache hits), the not-found billing caveat, and that trim=true preserves native save counts and keyword labels. Gaps remain on auth requirements and what the pins actually contain, but the operational cost behavior is well disclosed.

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?

Front-loaded with purpose, then route, then the trim behavior, then the billing model — a sensible ordering for an agent scanning for relevance. The billing sentences are slightly verbose and repetitive ('Errors, blocked or timed-out requests, invalid requests and cache hits'), but each conveys information that affects invocation decisions.

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

Completeness3/5

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

For a three-parameter tool with no output schema and no annotations, the definition covers cost and the trim flag but says nothing about the shape of the returned pins, how many are returned per page, or what a board URL must look like beyond the schema example. It is adequate to invoke but not to predict the response.

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?

Schema coverage is already 100%, so baseline is 3; the description earns an extra point by explaining that trim=true causes save counts and keyword labels to be retained 'when available,' which is meaningfully richer than the schema's 'Set true for a trimmed response.' The cursor parameter and its paging role are left entirely to the schema.

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 specific verb and resource ('Get pins from a Pinterest board') and pins down the exact route (GET /v1/pinterest/board). It is clearly distinct from a search or a user-boards listing, though it never explicitly contrasts itself with the pinterest_search sibling.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose statement: an agent can infer 'use this when you have a board URL and want its pins.' There is no explicit when-to-use/when-not guidance, no pointer to pinterest_search or pinterest_user_boards as alternatives, and no note on when to page with cursor versus starting fresh.

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