Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage Pinterest boards

manage_pinterest_boards

List Pinterest board sections, create boards with public or protected privacy, and add sections to prepare a profile's Pinterest account for uploads.

Instructions

Pinterest boards of a profile's connected account (list them with get_pinterest_boards). list_sections (board_id): the board's sections, whose id goes in the upload's pinterest board section option. create_board (name, description, privacy PUBLIC|PROTECTED; default PUBLIC) and create_section (board_id, name) create them on the user's Pinterest account.

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": {
      "action": "<action>",
      "profile": "<profile>"
    },
    "name": "manage_pinterest_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate_board / create_section: the name.
actionYes
privacyNocreate_board: PUBLIC (default) or PROTECTED (secret).
profileYesUpload-Post profile name with Pinterest connected.
board_idNolist_sections / create_section: the board.
descriptionNocreate_board: the board description.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds real context beyond that: creation happens on the user's actual Pinterest account, and a section's id is the value consumed by the upload's pinterest board section option, which explains the cross-tool data flow. It omits error modes and rate limits, but that is a minor gap given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is dense with no filler, but the structure is a single telegraphic run-on mixing a fragment, an action list, and a cross-tool note, with list_sections leading ahead of the board-creation actions. A reader gets the content, but the ordering and punctuation make it harder to scan than it needs to be.

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

Completeness4/5

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

For a three-action tool with a small schema and an output schema, the description covers each action and its relevant parameters, and correctly avoids explaining return values. The only missing piece an agent might want is the prerequisite that the named profile must have Pinterest connected, which the profile parameter description partially supplies.

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

Parameters3/5

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

Schema description coverage is 83%, so the schema already documents name, board_id, profile, description and the privacy enum. The description restates which parameters apply to which action and repeats the PUBLIC default, adding only marginal meaning over the structured fields. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the three actions the tool performs (list_sections, create_board, create_section) and states the resource (Pinterest boards/sections of a profile's connected account). It also explicitly routes listing to the sibling get_pinterest_boards, so the boundary is clear. The opening clause is a fragment with no verb, which keeps it from a 5.

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

Usage Guidelines3/5

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

It gives one concrete routing rule: use get_pinterest_boards to list boards rather than this tool. For the remaining actions it only implies selection via the action enum, with no guidance on prerequisites (e.g. the Pinterest account must be connected to the profile) or when create_section is preferred over create_board.

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

Deploy Server

Other Tools