Skip to main content
Glama
Martin-Code202

pinterest-mcp

pinterest_board_pins

List pins from any Pinterest board using its ID or 'username/slug' path, with optional filters for media type and pagination.

Instructions

List pins from a Pinterest board. Accepts a numeric board id or a 'username/board-slug' path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardYesBoard id or path, e.g. 'nasa/space'.
limitNo
bookmarkNo
mediaTypeNoFilter results to a single media kind, or 'all'.all
Behavior2/5

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

With no annotations, the description carries the full burden but only states the core function. It does not disclose pagination behavior (bookmark), rate limits, error handling, or ordering of pins. The only behavioral hint is the accepted board id format, which is already in the schema, providing minimal extra value.

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?

The description is two short sentences, immediately stating the action and a key detail about accepted inputs. Every word earns its place with no redundancy or filler, making it highly concise and well-structured.

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

Completeness2/5

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

The tool has four parameters including a pagination bookmark, no output schema, and no annotations. The description is too minimal to cover pagination, return format, or error conditions, leaving significant gaps for an agent to invoke it correctly, especially for multi-page listing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (board and mediaType described). The description repeats the board id/path format already in the schema and does not clarify limit, bookmark, or mediaType semantics. Since it adds no meaning beyond the schema, it fails to compensate for the undocumented parameters.

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 clearly states the tool lists pins from a Pinterest board, with a specific verb and resource. It distinguishes itself from sibling tools like pinterest_get_pin (single pin) and pinterest_search (search), making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions no exclusions, prerequisites, or comparisons to sibling tools, so the agent receives no help deciding between board listing, searching, or related pins.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Martin-Code202/pinterest-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server