Skip to main content
Glama

List Pinterest boards

list_boards
Read-only

Retrieve the logged-in user's Pinterest boards with IDs, names, and pin counts to inspect available boards before reading images or extracting design tokens.

Instructions

Lists the logged-in user's Pinterest boards (id, name, pin count).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already establishes this as a safe, non-mutating operation, so the description's main added value is the returned field list and the 'logged-in user' scoping, which implies an auth requirement. It does not disclose pagination behavior, default page size, or what happens when the user has no boards or many more than the limit allows. With annotations covering the safety profile, this is adequate but thin.

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?

A single sentence that leads with the verb and resource and appends the useful field list in parentheses. Nothing is redundant and nothing is buried.

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 simple read-only list tool with no output schema, naming the returned fields and the ownership scope is a reasonable amount of coverage. The gaps are the undocumented limit/pagination parameter and the unstated authentication precondition, both of which an agent would need to invoke this correctly against real data.

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?

There is one parameter (limit, min 1, max 250, default 50) and schema description coverage is 0%, so the description is the only place this could be explained — and it says nothing about limiting or paging. It does add meaning about the returned fields, but that is output semantics, not parameter semantics. The agent has no textual guidance on what limit controls.

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 ('Lists ... Pinterest boards') plus a scope constraint ('the logged-in user's') that implicitly distinguishes it from the public-board sibling. It also names the returned fields (id, name, pin count), so an agent can tell what it gets. It stops short of naming the sibling it contrasts with, but the scope phrase does most of that work.

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?

Usage is implied rather than stated: an agent can infer this is the entry point for enumerating the authenticated user's boards, and 'logged-in user's' implies that authentication is a precondition. There is no explicit when-to-use versus alternatives (e.g., get_board_pins for pins, get_public_board for other users' boards) and no mention of what to do if auth is missing.

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