Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

Delete pin

delete_pin
DestructiveIdempotent

Delete one pin, from Pinterest too by default. Irreversible; confirm first.

    Use for a pin that should not exist, or to replace a published pin that
    needs a correction (published pins cannot be edited). Before a pin
    publishes, fix it with update_pin instead. Never use delete_board to
    remove one pin.

    Returns id, deleted, removed_from_pinterest, pinterest_pin_id and
    reason when nothing was removed upstream (not_published,
    simulated_sandbox, record_only, api_version_too_old). Fails with
    not_found for an unknown id and insufficient_scope without the
    destructive scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pin_idYesUUID of the pin, from list_pins or create_pin.
delete_from_pinterestNotrue (default) also removes the published pin from Pinterest; false keeps it live there and only deletes the PinBridge record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / delete_from_pinterest / description
      Added value: +"true (default) also removes the published pin from Pinterest; false keeps it live there and only deletes the PinBridge record."
    • addedInput schema / properties / pin_id / description
      Added value: +"UUID of the pin, from list_pins or create_pin."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds crucial context: it is irreversible, requires confirmation, and details the return values and failure modes (not_found, insufficient_scope, and reasons when nothing was removed upstream). This goes well beyond the annotation metadata and fully discloses the operation's side effects and error behavior.

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?

The description is organized into a brief lead sentence followed by usage guidance and return/error details. Every sentence adds value, and the most important information (irreversibility, primary action) is front-loaded. It is concise given the behavioral complexity it must convey.

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?

With no output schema, the description fully explains the return payload and error conditions. It covers usage, exclusions, and scope requirements, leaving no critical gap an agent would need to guess. The description is complete for a destructive operation with subtle edge cases.

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 coverage is 100%, so the schema already documents both pin_id and delete_from_pinterest with their meanings and defaults. The description does not add additional parameter semantics beyond what the schema provides, so a baseline 3 is appropriate since the schema carries the burden.

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 (delete) and resource (pin), and immediately clarifies the default behavior of also removing from Pinterest. It explicitly differentiates from delete_board and update_pin by naming when each alternative is appropriate, so an agent can disambiguate without inspecting sibling 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 explicit conditions for use (pin should not exist, or replace a published pin that cannot be edited) and explicit exclusions (before publishing, use update_pin; never use delete_board for a single pin). This fully covers when and when-not, including naming the correct alternative.

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