Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

pinterest_user_boards

Retrieve a Pinterest user's boards by username to view and analyze their curated collections. Provide a handle to get the board list, with an optional trimmed response.

Instructions

pinterest: User Boards. GET /v1/pinterest/user/boards. Get a user's boards 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": {
      "handle": "<handle>"
    },
    "name": "pinterest_user_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet true for a trimmed response.
handleYesPinterest username, e.g. broadstbullycom, not a profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by disclosing the credit cost model: 1 credit on success, free on errors, blocked, timed-out, invalid requests and cache hits. It says nothing about pagination, result volume, rate limits, or what a board record contains, which matters for a list-returning endpoint.

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?

The purpose is front-loaded in the first two sentences, and the cost sentences, while wordy, carry information the agent cannot get elsewhere. The endpoint path restates the tool name but is short enough not to be wasteful.

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 two-parameter read tool with no output schema and no annotations, the definition covers billing well but never indicates what comes back (a list of boards, pagination behavior, or what trim changes in the response). An agent can call it, but cannot predict the shape of the result.

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%, so both parameters (handle, trim) are already documented with an example and a clear warning that handle is not a profile URL. The description adds no further meaning about either parameter, 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 gives a specific verb and resource ("Get a user's boards") plus the underlying endpoint GET /v1/pinterest/user/boards, so the operation is unambiguous. It does not distinguish itself from the sibling pinterest_board (singular), leaving the agent to infer that this returns a list rather than one board.

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 statement of when to choose this tool over pinterest_board or pinterest_search, and no prerequisites such as whether the handle must be a plain username. The only guidance offered is billing behavior, which tells the agent nothing about selection.

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