pinterest-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_READ_ONLY | No | Refuse anything that changes state. Set to 1 to enable. | 0 |
| MCP_NO_DESTRUCTIVE | No | Allow writes, refuse anything irreversible or chargeable. Set to 1 to enable. | 0 |
| PINTEREST_BASE_URL | No | Defaults to https://api.pinterest.com/v5. Point at https://api-sandbox.pinterest.com/v5 for the sandbox. | https://api.pinterest.com/v5 |
| PINTEREST_ACCESS_TOKEN | Yes | Required. An OAuth2 access token for your app. | |
| PINTEREST_AD_ACCOUNT_ID | No | Optional. 148 operations are scoped to an ad account; set this and it is filled in when omitted. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pinterest_list_operationsA | Browse the Pinterest API — 263 of 266 operations are reachable here. 131 of them are advertising and need an ad account; the rest are the organic surface (pins, boards, media, search, analytics). Use this to find an operation id for pinterest_call. |
| pinterest_callC | Call any Pinterest operation by id. ad_account_id is filled in from PINTEREST_AD_ACCOUNT_ID when you leave it out. |
| pinterest_get_meD | The authenticated Pinterest account. |
| pinterest_list_boardsC | Boards belonging to the authenticated account. |
| pinterest_list_pinsC | Pins belonging to the authenticated account. |
| pinterest_create_pinA | Create a pin on one of your boards. The image must be a publicly reachable URL — Pinterest fetches it server-side, so a local file path will not work. |
| pinterest_get_pin_analyticsC | How a pin has performed. Reads only, so it works under MCP_READ_ONLY. |
| pinterest_search_my_pinsC | Search your own pins by term. |
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 8 tools
Each convenience tool targets a distinct Pinterest resource (create pin, pin analytics, search pins, list boards, list pins, get account), and list_operations/call form a clear discovery/execution pair. The only soft spot is that pinterest_call can also perform operations that have dedicated wrappers, so an agent must decide between the generic and specific path.
Tool names use a consistent pinterest_ + verb + noun pattern in snake_case, such as create_pin, list_boards, and get_pin_analytics. Minor inconsistencies exist: pinterest_call lacks a target noun, and search_my_pins mixes a possessive modifier while similar tools don't.
Eight tools is a compact, well-scoped set for a Pinterest server. The design intentionally avoids hundreds of individual tools by providing pinterest_list_operations and pinterest_call as a generic discovery/execution pair.
The server exposes 263 of 266 Pinterest API operations through pinterest_call, making the surface nearly exhaustive. Convenience wrappers cover common pin, board, and account workflows, while pinterest_list_operations prevents dead ends by enabling operation discovery.