Skip to main content
Glama
Hermoso

Hermoso

Official

List Pinterest boards

list_pinterest_boards
Read-onlyIdempotent

Lists Pinterest boards (ID, name, privacy, pin count) on a connected account so users can choose one before posting pins. Read-only; requires Pinterest connected.

Instructions

List the boards on the user’s connected Pinterest account — id, name, privacy and pin count. ALWAYS call this before post_to_pinterest and let the USER pick: Pinterest requires a board and Hermoso never chooses one for them. Read-only, 0 credits. Needs Pinterest connected (Connectors > Pinterest).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pinterest_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNowhich connected account: its @handle or id from list_connector_accounts; needed only when several are connected
privacyNofilter by board privacy; default is everything the connection can see

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "which connected account: its @handle or id from list_connector_accounts; needed only when several are connected",
      +  "type": "string"
      +}
  2. Addedv0.1.161

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotent, non-destructive, so safety is covered; the description adds value beyond that with cost ("0 credits"), an auth/setup requirement (Connectors > Pinterest), and a behavioral constraint that the agent must never auto-select a board.

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?

Three short sentences, front-loaded with purpose, then the mandatory ordering rule, then cost and prerequisite. Every clause carries operational information; no 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, and the description compensates by naming the fields returned. With only 2 optional, fully documented parameters and annotations covering the safety profile, an agent has everything needed to call this 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%, with both account and privacy already documented including the enum values and default. The description adds no further syntax or filtering guidance, so the schema baseline 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?

Specific verb + resource ("List the boards on the user's connected Pinterest account") plus the returned fields (id, name, privacy, pin count). It also distinguishes the tool from post_to_pinterest, so an agent can place it in the workflow without opening the schema.

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 when-to-use: ALWAYS call this before post_to_pinterest, and let the USER pick the board rather than choosing one. Prerequisite (Pinterest must be connected via Connectors) is stated, and the sibling it pairs with is named, leaving nothing to inference.

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