Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Pinterest board pins

pinterest_board_pins_list
Read-onlyIdempotent

Lists public pins from a Pinterest board URL and supports cursor pagination to retrieve additional results.

Instructions

List public pins on a Pinterest board by URL. Requires url. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "pinterest_board_pins_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Pinterest board.
trimNoWhen true, returns a smaller response with fewer fields.
cursorNoOpaque pagination cursor returned by a previous response.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the useful constraint that only public pins are returned and that pagination is cursor-driven, but it says nothing about empty boards, private/invalid URLs, or result shape beyond 'a list'.

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?

Two short sentences with no filler: the scope constraint is front-loaded, the required input follows, and the return/pagination note comes last. Nothing is redundant or padded.

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

Completeness4/5

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

For a simple read-only list endpoint with full schema coverage and no output schema, the description covers purpose, the required input, and the pagination contract. Minor omission: it does not mention that the response is a partial page and must be re-called with the returned cursor, though 'use cursor when paginated' gestures at it.

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 every parameter including trim, cursor and the context/llm_model plumbing is already documented in the schema. The description only restates that url is required and mentions cursor for pagination, adding essentially no meaning beyond the structured data.

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?

States a specific verb and resource ('List public pins on a Pinterest board') plus the scoping constraint 'public' and the input mode 'by URL'. It is clearly distinct from pinterest_search_pins_list and pinterest_profile_boards_list in substance, though it never names those siblings explicitly.

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?

Implied usage only: it tells the agent that a board URL is required and that a cursor handles pagination, which implicitly distinguishes it from a search tool. There is no explicit statement of when to choose this versus pinterest_search_pins_list, and no prerequisites or failure conditions are given.

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