Skip to main content
Glama

Search my saved pins

search_my_pins
Read-only

Search only the pins saved by the logged-in user to find relevant images and board items; restrict results to saved content instead of public Pinterest search.

Instructions

Searches the pins the logged-in user has saved (not all of Pinterest — the public search API needs special partner access).

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": {
      "query": "<query>"
    },
    "name": "search_my_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
max_imagesNo
include_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context beyond that — it does so by scoping results to the authenticated user's own pins and noting the partner-access constraint on public search. It stops short of describing result ordering, pagination across the limit, or what the image-related parameters do to the response.

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?

A single sentence with the core scope claim front-loaded and the qualifier in a parenthetical; nothing is redundant. Slightly terse given the undocumented parameters, but the structure itself is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with no output schema and zero parameter documentation, the description leaves the agent guessing about page size, image embedding, and return shape. The auth-scope and public-API notes are helpful but insufficient to call this tool correctly with the image parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description says nothing about query, limit, include_images, or max_images. The presence of image parameters on a pin-search tool is non-obvious and undocumented anywhere, so the description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("searches the pins the logged-in user has saved") and bounds the scope against public Pinterest search. It is clear what the tool returns conceptually, though it never contrasts with the sibling get_board_pins, which is the nearest scope-confusable alternative.

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

Usage Guidelines3/5

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

The parenthetical gives an implicit when-to-use (saved pins rather than global search) and explains why the public equivalent is unavailable. However, there is no explicit guidance on when to prefer get_board_pins or get_pin over this search, and no mention of auth prerequisites despite the "logged-in user" framing.

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