Skip to main content
Glama
hermoso-ai

Hermoso

Official

Delete a Pin

delete_pinterest_pin
DestructiveIdempotent

Permanently delete a Pinterest pin after verifying its details. First call returns the title, saves, and promoted status; second call with confirm and exact title finalizes deletion.

Instructions

PERMANENTLY delete a Pin. Pinterest has no undelete and no archive for one. Call it WITHOUT confirm first: nothing is deleted, and it answers with the Pin’s real title, its lifetime saves and impressions, and whether it HAS BEEN PROMOTED in an ad — all read back from Pinterest. Show the user that, get an unambiguous yes, then call again with confirm:true plus confirmName (its exact title) once it has saves or has been promoted, because confirming that you meant to delete SOMETHING does not prove you aimed at the right Pin. DELETING A PIN THAT AN AD PROMOTES pulls the creative out from under that ad, so check the promoted flag before agreeing. The verdict is read back from Pinterest, never taken from its 2xx. 0 credits. Needs Pinterest connected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinIdYesnumeric Pin id from list_pinterest_pins
confirmNoREQUIRED true — deletion is permanent
confirmNameNothe Pin’s EXACT title as the unconfirmed call reported it — required once it has saves or has been promoted
Behavior5/5

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

Goes far beyond annotations by detailing the non-destructive first call, the authoritative response source ('read back from Pinterest, never taken from its 2xx'), the impact on ads, and the zero-credit cost. This is comprehensive behavioral disclosure for a destructive action.

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?

The description is longer than average (5 sentences) but every sentence serves a distinct purpose: permanence, two-phase flow, promoted-pin risk, and authoritative response. It is structured logically and front-loads the core purpose, though it could be tightened slightly.

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 no output schema, the description explicitly states what the unconfirmed call returns (title, saves, impressions, promoted flag) and how to interpret the verdict. It covers prerequisites, side effects, and the safety mechanism—complete for an agent to execute correctly.

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 description coverage is 100% and already explains each parameter, including conditions for confirmName. The description adds the rationale—why confirmName is needed to ensure targeting the correct pin—and explains the flow, providing value beyond the schema.

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?

The description opens with 'PERMANENTLY delete a Pin'—a specific verb, resource, and critical qualifier. It also distinguishes itself from other delete tools by emphasizing the permanence and lack of undo, which is unique to this tool among siblings.

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?

Provides an explicit two-phase workflow: call without confirm to retrieve metadata, then call with confirm and confirmName after user consent. It also states prerequisites ('Needs Pinterest connected') and warns about promoted pins, leaving no ambiguity about when or how to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server