Skip to main content
Glama

Get pins from a board

get_board_pins
Read-only

Retrieve pins from a Pinterest board, optionally including actual images so AI assistants can view designs and use them for UI or visual inspiration.

Instructions

Gets pins from a board. With include_images=true, the actual images are returned so the model can see the designs (use this for UI/visual inspiration).

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_id": "<board_id>"
    },
    "name": "get_board_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
board_idYes
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

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does meaningful work: it discloses that images are actually attached to the result and implicitly warns that images consume context via the schema note. It still omits return shape beyond images and any pagination behavior for limit.

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?

Two short sentences, purpose front-loaded, with the practical hint parenthesized at the end. Nearly zero waste, though the opening clause largely restates the title.

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 read-only list tool with no output schema, the definition covers the key behavioral surprise (images returned, context cost) but leaves the limit parameter and result ordering/truncation undocumented. Adequate but with visible gaps an agent would hit on first call.

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 25% — only max_images is documented in the schema. The description compensates for exactly one parameter by explaining what include_images does, but limit, board_id, and the interplay between include_images=true and max_images are left to the schema alone.

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: 'Gets pins from a board.' That distinguishes it from get_pin (single pin) and get_public_board (different board scope), 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?

Provides one concrete usage hint: use include_images=true 'for UI/visual inspiration,' which is a real when-to-use signal. It gives no guidance on when to prefer this over get_public_board or search_my_pins, and no exclusions or prerequisites.

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