Skip to main content
Glama

Get a pin

get_pin
Read-only

Retrieves a single Pinterest pin’s details and optionally its image so AI assistants can inspect board content and extract design tokens.

Instructions

Gets one pin's details and (optionally) its image.

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": {
      "pin_id": "<pin_id>"
    },
    "name": "get_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pin_idYes
include_imageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one piece of behavioral context beyond that: the returned payload may include image data, gated by a flag, which matters because image bytes make responses heavy. It says nothing about behavior when the pin is missing, auth failure, or response shape, so it is additive but thin.

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 front-loaded sentence with zero filler; the core resource comes first and the optional behavior is parenthetical. It is efficient to the point of terseness, but no sentence is wasted or buried.

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

Completeness3/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 an annotation covering safety and no output schema, the definition is minimally adequate. Missing are the include_image default semantics, behavior on an unknown pin_id, and any note that the payload differs substantially depending on that flag — meaningful for an agent deciding whether to request images.

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 0%, so both parameters rely on the description. "one pin's" maps to pin_id and "(optionally) its image" maps to include_image, which is useful. However, the description omits the actual default (include_image defaults to true, so images are returned unless suppressed) and gives no ID format or size hints, leaving real ambiguity for a tool where images are presumably costly.

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?

"Gets one pin's details" states a specific verb (get) and resource (a single pin), and the singular "one pin" distinguishes it from list-style siblings such as get_board_pins or search_my_pins. It never names an alternative explicitly, so it lands at clear-but-undifferentiated rather than fully disambiguating.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no when-not-to-use, and no mention of any sibling. An agent can infer that this retrieves a single pin by ID, but nothing tells it to prefer this over get_board_pins or search_my_pins, nor what precondition (a known pin_id, auth) is required.

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