Skip to main content
Glama

AIsa Pinterest

by one.aisa
OverviewDiscussionsAdmin

boards

get_pinterest_user_boards
Read-onlyIdempotent

Lists a user's public boards by username, with a cursor to page. Each board carries id, name, url, description, pin_count, follower_count, section_count, collaborator_count, privacy, owner, created_at, cover_pin and cover_images. Measured at 59 KB for 10 boards; trim=true collapses it to 3.3 KB — the largest trim ratio in this API — keeping id, name, url, description, pin_count, follower_count, created_at and image_cover_hd_url. The handle is the bare username as it appears in a profile URL (agkelsey, not a full URL). Feed each board's url to get_pinterest_board to read its pins; to search across all of Pinterest use get_pinterest_search.

Usage-based billing; Default request estimate: $0.00188 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true for a trimmed down version of the response
handleNoThe username of the user to get boards for. (e.g. broadstbullycom from https://www.pinterest.com/broadstbullycom/)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / handle / description
      Added value: +"The username of the user to get boards for. (e.g. broadstbullycom from https://www.pinterest.com/broadstbullycom/)"
    • addedInput schema / properties / trim / description
      Added value: +"Set to true for a trimmed down version of the response"
  2. Changed6 schema fields changed
    • removedInput schema / properties / handle / description
      Removed value: -"The username of the user to get boards for. (e.g. broadstbullycom from https://www.pinterest.com/broadstbullycom/)"
    • removedInput schema / properties / handle / example
      Removed value: -"broadstbullycom"
    • removedInput schema / properties / trim / description
      Removed value: -"Set to true for a trimmed down version of the response"
    • removedInput schema / properties / trim / example
      Removed value: -"false"
    • changedInput schema / properties / trim / type
      Previous value: -"boolean"New value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "handle"
-]New value: +[]
  3. Changed2 schema fields changed
    • addedInput schema / properties / handle / example
      Added value: +"broadstbullycom"
    • addedInput schema / properties / trim / example
      Added value: +"false"
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, yet the description adds real behavioral detail: response payload size (59 KB for 10 boards), the trim ratio and exactly which fields survive trimming. This is the kind of operational context an agent needs to avoid oversized responses.

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 output fields, then the trim tradeoff, then routing. Dense but nearly every sentence earns its place; the trailing pricing boilerplate is injected and slightly dilutes the structure.

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?

Pagination (cursor), input format, response shape, payload-size tradeoff, and sibling routing are all covered. With an output schema present, return values need not be explained, and the extra field listing is a bonus rather than a gap.

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 baseline is 3, but the description goes beyond the schema's terse 'trimmed down version' by naming the exact fields trim keeps, and reinforces that handle is a bare username rather than a profile URL.

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: 'Lists a user's public boards by username, with a cursor to page.' It also names the sibling tools it is not (get_pinterest_board for pins, get_pinterest_search for cross-Pinterest search), so an agent can route correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives with conditions: feed each board's url to get_pinterest_board for pins, use get_pinterest_search for Pinterest-wide search. It also clarifies the expected handle input format. There are no explicit when-not-to-use statements, but the alternative routing is clear.

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

All AIsa Pinterest 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