Skip to main content
Glama

Get a public board (no login)

get_public_board
Read-only

Read any public Pinterest board or profile from a link without login or API keys, returning up to ~25 recent pins with images so the model can view them.

Instructions

Reads any PUBLIC Pinterest board or profile from its link, with no login or keys. Returns the latest ~25 pins, with images attached so the model can see them. Accepts board URLs on any Pinterest domain, pin.it short links, or 'username/board-name'. Prefer this tool when the user shares a board link.

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": {
      "board_url": "<board_url>"
    },
    "name": "get_public_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
board_urlYese.g. https://www.pinterest.com/username/board-name/ or username/board-name
max_imagesNoHow many images to attach (images use context).
include_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 and openWorldHint, so the safety profile is covered; the description adds real context on top: no authentication or API keys needed, an approximate return size (~25 latest pins), and that images are attached and therefore consume model context. It does not say how private/deleted boards fail or whether any rate limiting applies.

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?

Four short sentences, each carrying distinct information: capability, return shape, input formats, and selection preference. The ordering is front-loaded with what the tool is and what it gives back, with the routing hint last.

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?

With no output schema, the description carries the burden of describing returns and does so (latest ~25 pins plus attached images). Combined with annotations this is nearly complete for a read-only fetch tool; the remaining gap is failure behavior for private or invalid boards.

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 50%, and the description compensates for the most important gap by enumerating accepted board_url forms, including pin.it short links and any Pinterest domain, which the schema example does not mention. The '~25 pins' phrasing also contextualizes the limit default. include_images and max_images are only obliquely covered via 'images attached'.

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?

The description opens with a specific verb and resource ('Reads any PUBLIC Pinterest board or profile from its link') and constrains scope to public content. It implicitly separates itself from the login/auth siblings by stating 'no login or keys', and it discloses that profiles are also accepted, which the name alone would not reveal.

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?

It gives a clear selection rule: 'Prefer this tool when the user shares a board link.' That covers the common trigger well, but there is no explicit when-not guidance (e.g. what to use for the authenticated user's own boards, or when a board turns out to be private), and no sibling is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.