Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

List Pinterest Boards

list_pinterest_boards
Read-onlyIdempotent

Retrieve a connected Pinterest account's boards, including secret boards, with IDs and privacy details so you can choose the correct board before scheduling or publishing a post.

Instructions

List the boards of a connected Pinterest account, secret boards included. Returns { boards } with id, name, description, privacy (PUBLIC, PROTECTED or SECRET) and pinCount. Call it before posting to Pinterest, ask the user which board to pin to unless they already named one, and pass that board's id as pinterestConfigs[].boardId in create_post, update_post or bulk_schedule_posts. When the user named a board you may pass that name as boardName instead, never both; a name that matches no board, or several, fails with 400 and nothing falls back. A board belongs to one Pinterest account, so call it once per Pinterest account. A post sent without boardId or boardName goes to a public board named AdaptlyPost, which is created on first use. Fails with 404 when accountId is not a Pinterest account in the workspace, and with 400 when Pinterest refuses the request, which usually means the user must reconnect the account in AdaptlyPost. Nothing is posted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe Pinterest account id from list_accounts
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with boards: one { id, name, description, privacy, pinCount } per board. Pass id as pinterestConfigs[].boardId, or name as boardName.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description goes well beyond them: it discloses the default AdaptlyPost board created on first use, the 404 condition (accountId not a Pinterest account in the workspace), the 400 condition and its remedy (reconnect the account), and closes with 'Nothing is posted.' These are exactly the failure and side-effect details an agent cannot derive from 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 purpose, then usage, then failure modes — a sensible ordering with no filler sentences. It is dense and long, and restating the return payload ('Returns { boards } with id, name, description, privacy... and pinCount') duplicates the output schema, which is the one place it could be trimmed.

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?

For a two-parameter read tool with full schema coverage, full annotation coverage and an output schema, the definition covers purpose, prerequisites, downstream usage, exclusivity rules, default behavior and error recovery. Nothing an agent needs in order to call it correctly and interpret failures is missing.

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%, so both parameters are already documented; the description still adds real meaning by constraining accountId to a Pinterest account and stating 'call it once per Pinterest account', which implies a per-account call pattern rather than one call across accounts. It says nothing extra about workspaceId, relying on the schema there, which is acceptable.

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?

Opens with a specific verb+resource+scope: 'List the boards of a connected Pinterest account, secret boards included.' This is unmistakably distinct from siblings such as list_posts or list_accounts, and the 'secret boards included' clause pre-answers the most likely scoping question.

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 when-to-use ('Call it before posting to Pinterest'), an interaction rule ('ask the user which board to pin to unless they already named one'), the exact downstream wiring ('pass that board's id as pinterestConfigs[].boardId in create_post, update_post or bulk_schedule_posts'), and the boardId-vs-boardName exclusivity rule with its 400 failure mode. Alternatives and their preconditions are named rather than inferred.

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