AIsa Pinterest

board

get_pinterest_board

Read-onlyIdempotent

Returns one page of pins from a board URL, with a cursor to page. Board pins carry a third field subset, different from both search results and pin detail: node_id, link, domain, rich_summary, seo_url, board and auto_alt_text among them. Measured at 104 KB for 16 pins; trim=true cuts it to 28 KB, keeping per pin id, title, description, link, domain, board, pinner, alt_text, rich_summary and reaction_counts. Board URLs come from board.url on search results — relative, like /agkelsey/the-apartment/, so prefix https://www.pinterest.com — or from get_pinterest_user_boards. For a user's board list rather than one board's pins, use get_pinterest_user_boards.

Usage-based billing; Default request estimate: $0.00188 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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>"
    },
    "name": "get_pinterest_board"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The URL of the board to get
`trim`	No	Set to true for a trimmed down version of the response
`cursor`	No	The cursor to get the next page of results

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "url"
+]
```

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "The cursor to get the next page of results",
+  "type": "string"
+}

addedInput schema / properties / trim / description

Added value: +"Set to true for a trimmed down version of the response"

addedInput schema / properties / url / description
```
Added value: +"The URL of the board to get"
```

Changed7 schema fields changedOct 15, 2026

removedInput schema / properties / cursor

Removed value: -{
-  "description": "The cursor to get the next page of results",
-  "example": "Y2JURlEwTWsxNlp6Vk9SR2MwV....",
-  "type": "string"
-}

removedInput schema / properties / trim / description

Removed value: -"Set to true for a trimmed down version of the response"

removedInput schema / properties / trim / example
```
Removed value: -"false"
```

changedInput schema / properties / trim / type

Previous value: -"boolean"New value: +"string"

removedInput schema / properties / url / description
```
Removed value: -"The URL of the board to get"
```

removedInput schema / properties / url / example

Removed value: -"https://www.pinterest.com/lizmrodgers/moms-night/"

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[]

Changed3 schema fields changedSep 18, 2026
- addedInput schema / properties / cursor / example
```
Added value: +"Y2JURlEwTWsxNlp6Vk9SR2MwV...."
```
- addedInput schema / properties / trim / example
```
Added value: +"false"
```
- addedInput schema / properties / url / example
```
Added value: +"https://www.pinterest.com/lizmrodgers/moms-night/"
```
First observedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare this as a safe, read-only, idempotent, open-world operation, but the description adds substantial behavior context. It explains pagination via cursor, response size (104 KB for 16 pins), the effect of trim=true (28 KB), and the exact per-pin fields preserved when trimming.

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?

The description is front-loaded with the core purpose and pagination behavior, then adds useful field and size details. It is somewhat long and includes pricing boilerplate, but most sentences carry actionable information.

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

Completeness5/5

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

Given the available annotations, 100% schema coverage, and an output schema, the description provides everything needed to invoke the tool correctly. It covers URL sourcing, pagination, trimming, response size, field differences, and the relevant sibling alternative.

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 100%, so the schema already defines all three parameters. The description still adds meaningful semantics, especially URL format and source, trim behavior and field retention, and cursor paging context, though cursor mechanics are only lightly described.

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 that the tool returns one page of pins from a board URL, with a cursor for pagination. It distinguishes this tool from search results and pin detail by noting the different field subset, and explicitly separates it from get_pinterest_user_boards for board lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where board URLs come from: board.url on search results, including the relative-path prefix rule, or get_pinterest_user_boards. It also explicitly says to use get_pinterest_user_boards when the user wants a board list rather than one board's pins.

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

All AIsa Pinterest tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?