Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

Delete board

delete_board
DestructiveIdempotent

Delete a board on Pinterest together with every pin on it. Irreversible; confirm first.

    Use only when the whole board should go; to remove one pin use
    delete_pin. PinBridge keeps its records of the board's published pins
    and flags them removed_from_pinterest_at.

    Returns {"deleted": true, "board_id": "<id>"}. Fails with
    board_not_found for an unknown board, forbidden when sandbox board
    writes are blocked, insufficient_scope without the destructive scope,
    and token_expired / scope_missing when the Pinterest connection needs a
    reconnect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesPinterest board ID (numeric string), from list_boards.
account_idYesUUID of a connected Pinterest account, from list_pinterest_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / account_id / description
      Added value: +"UUID of a connected Pinterest account, from list_pinterest_accounts."
    • addedInput schema / properties / board_id / description
      Added value: +"Pinterest board ID (numeric string), from list_boards."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses irreversibility and the need to confirm first, the side effect on PinBridge's records, exact success return shape, and all relevant failure modes including scope and token issues. This is substantial behavioral context that annotations alone do not provide.

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

Conciseness5/5

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

Front-loaded with the action, scope, and irreversibility; then usage guidance, side effects, and error cases are clearly separated. Every sentence adds operational value, and the structure makes it easy to scan.

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?

Despite lacking an output schema, the description provides the return format and error names. It also covers the destructive side effect and the account-scope context. An agent has everything needed to select and invoke this tool correctly.

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 100%, and both parameters are already documented with provenance (from list_boards / list_pinterest_accounts). The description adds no new parameter-level detail, so the baseline score of 3 applies.

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 and resource ('Delete a board on Pinterest'), clarifies the scope ('together with every pin on it'), and explicitly names the sibling it is not ('to remove one pin use delete_pin'). An agent can distinguish this from delete_pin and similar tools without opening schemas.

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?

Gives an explicit when-to-use condition ('Use only when the whole board should go') and the alternative for the other case ('to remove one pin use delete_pin'). This is direct, unambiguous routing guidance.

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