pinterest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINTEREST_COOKIE | Yes | Your Pinterest session cookie, equivalent to your login session. Keep secret. | |
| PINTEREST_DOMAIN | No | The Pinterest domain to use. Defaults to www.pinterest.com. If Pinterest redirects you to a country-specific domain when logged in (e.g. in.pinterest.com), use that instead. | www.pinterest.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pinterest_imagesB | Search Pinterest for |
| get_pinterest_boardsA | List a Pinterest user's boards with url and pin count. |
| get_pinterest_board_infoA | Look up a Pinterest board's name and total pin count from its URL (accepts pin.it short links). |
| fetch_pinterest_boardB | Download up to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear purpose: search images, list boards, get board info, and fetch board images. The slight overlap between search_pinterest_images and fetch_pinterest_board (both download images) is mitigated by their distinct sources (query vs. board). No two tools are truly confusing.
All names follow a verb_noun pattern (search, get, fetch). However, there is a mix of 'get' and 'fetch' for similar actions, and 'get_pinterest_boards' vs 'get_pinterest_board_info' could be slightly more distinctive. Still, the pattern is consistent enough for an agent to predict behavior.
Four tools is a reasonable scope for a Pinterest-focused server. It covers the core actions of searching and retrieving board content without being overly sparse or bloated. The count fits well within the typical 3-15 range.
The server covers browsing and downloading images from searches and boards, but lacks operations for pin-level details, user profiles, or any create/update/delete actions. For a read-only image-centric tool, it's decent, but there are noticeable gaps for a full Pinterest API surface.