pinterest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLEET_BOARD_URL | No | Base URL of the fleet board for capability and publish-clearance checks. | http://127.0.0.1:8420 |
| PINTEREST_SERVER_BRAND | No | Brand name required for publish-clearance checks. | with_nate |
| PINTEREST_CREDENTIALS_FILE | Yes | Path to the credentials file containing PINTEREST_APP_ID, PINTEREST_APP_SECRET, PINTEREST_ACCESS_TOKEN, PINTEREST_REFRESH_TOKEN, PINTEREST_TOKEN_EXPIRES_AT. The server reads and rewrites this file when refreshing tokens. |
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_get_user_infoA | Get the current Pinterest account's basic info (username, id, account type). Safe read. Use to confirm the credentials point at the intended account before any write. |
| pinterest_list_boardsA | List the account's boards, paginated. Safe read. Use before creating a pin to find the board_id you want to pin to — the create-pin call needs it. |
| pinterest_get_boardA | Fetch one board's details by id. Safe read. |
| pinterest_list_pinsA | List pins on the account, optionally scoped to a single board via board_id. Safe read. |
| pinterest_get_pinA | Fetch one pin's details by id. Safe read. |
| pinterest_get_pin_analyticsA | Engagement metrics for one of our own pins (impressions, saves, pin clicks, outbound clicks, video views). Safe read. This is the native Etsy-driver measurement — outbound clicks on a pin whose link points at an Etsy listing are the traffic-lever signal. |
| pinterest_create_boardA | Create a new Pinterest board on the account. Live, immediately visible on the profile if privacy=PUBLIC. Requires agent_id (must hold 'social') and task_id (task must be cleared for the with_nate brand — Done and carrying an approved output). |
| pinterest_create_pinA | Publish a real, immediately-live pin to one of our boards. Requires agent_id (must hold 'social') and task_id (task must be cleared for the with_nate brand). No draft state — once this returns success, the pin is on the account. image_url must be a PUBLIC http(s) URL that Pinterest can fetch server-side; a local file path will NOT work. The 'link' field is the destination URL when someone clicks the pin (e.g. the Etsy listing URL) — put it there, not in the description, or click-through analytics count nothing. |
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 tool targets a distinct resource and action: single-item reads (pin, board, user), list operations (boards, pins), analytics, and creation (board, pin). The descriptions clarify use cases, e.g., list_boards for finding board_id before create_pin, so there is no real ambiguity.
All tools follow the same 'pinterest_{verb}_{noun}' pattern with lowercase snake_case. Verbs are consistently get, list, or create, and nouns are clear resources. No mixed conventions or vague names.
Eight tools is well-scoped for a Pinterest management server. It covers authentication check, reading user/boards/pins, analytics, and creating boards/pins—enough to perform the advertised workflow without redundancy or bloat.
The set covers the core workflow: list boards to get IDs, create boards and pins, fetch pin data, and retrieve analytics. Missing update/delete operations are a minor gap, but the described use case (publishing live pins and measuring traffic) is fully supported.