Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

Update board

update_board
DestructiveIdempotent

Rename a board or change its description or privacy on Pinterest.

    Use for board housekeeping; pins on the board are untouched. To move a
    pin that has not published between boards use update_pin; to remove a
    board use delete_board.
    Pass at least one of name, description or privacy.

    Returns the updated board (id, name, description, privacy). Fails with
    board_not_found for an unknown board, forbidden when sandbox board
    writes are blocked, and token_expired / scope_missing when the
    Pinterest connection needs a reconnect (including SECRET on an account
    connected without boards:write_secret).

Input Schema

NameRequiredDescriptionDefault
nameNoNew board name, unique within the account.
privacyNo"PUBLIC" or "SECRET". SECRET needs the boards:write_secret permission; older connections fail with scope_missing until reconnected.
board_idYesPinterest board ID (numeric string), from list_boards.
account_idYesUUID of a connected Pinterest account, from list_pinterest_accounts.
descriptionNoNew board description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / privacy / description
      Previous value: -"\"PUBLIC\" or \"SECRET\"."New value: +"\"PUBLIC\" or \"SECRET\". SECRET needs the boards:write_secret permission; older connections fail with scope_missing until reconnected."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint=false, idempotentHint=true and destructiveHint=true, the description still adds substantial non-annotation context: pins are untouched, the board_not_found/forbidden/scope_missing failure modes, and the boards:write_secret reconnect requirement. This is genuine behavioral disclosure beyond the structured fields.

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 the routing sentence before the required-parameter rule and error list. The error enumeration is dense but each clause is actionable; slightly long, though nothing is pure filler.

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?

No output schema exists, so the description carries the return value ('updated board (id, name, description, privacy)') and documents the failure modes and permission prerequisites. Complete for a mutation tool of this complexity.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds a real constraint not visible in the schema: at least one of name/description/privacy must be passed (the schema marks all three nullable/optional). That is added meaning beyond the field 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 ('rename') plus resource ('board') and enumerates the mutable fields (name, description, privacy). It explicitly differentiates from siblings by naming update_pin and delete_board with the conditions that select them.

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?

Explicit 'use for board housekeeping', names the alternatives (update_pin to move an unpublished pin, delete_board to remove) and gives the required-parameter constraint. An agent can route correctly without reading any other tool.

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

All pinbridge toolsInspect
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