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.

Input Schema

Name	Required	Description
`url`	No	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.

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.7/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered elsewhere. The description adds substantial behavioral context beyond that: pagination via cursor, concrete payload sizes (104 KB for 16 pins; 28 KB trimmed) and the exact field subsets returned. It stops short of stating rate limits or error behavior, so a 4 rather than 5.

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?

Front-loaded with the core action and paging behavior, and every sentence carries information. The two inline field enumerations ('node_id, link, domain...' and the trim field list) are dense and slightly bloat the text, and the injected pricing boilerplate sits outside the definition's control.

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?

An output schema already exists, so return values need no further explanation, and annotations cover the read-only/idempotent profile. Between the URL-source guidance, paging semantics and field-set/size notes, nothing needed to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: url must be absolute, with relative board paths needing an https://www.pinterest.com prefix, and trim=true is quantified as cutting 104 KB to 28 KB while enumerating the retained fields. This goes well beyond the schema's one-line parameter docs.

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?

States a specific verb and resource — 'returns one page of pins from a board URL' — and immediately differentiates from siblings by noting it also emits a paging cursor and that board pins use a distinct field subset from search results and pin detail. An agent can distinguish it from get_pinterest_search and get_pinterest_user_boards without opening schemas.

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?

Explicitly routes the agent: 'For a user's board list rather than one board's pins, use get_pinterest_user_boards,' and explains where valid URLs originate (board.url on search results, or get_pinterest_user_boards). Both when-to-use and the alternative are named.

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?