Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Pinterest pin

pinterest_pin_get
Read-onlyIdempotent

Fetch a public Pinterest pin by URL to retrieve its details for content research, reference, or sharing.

Instructions

Fetch a public Pinterest pin by URL. Requires url.

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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "pinterest_pin_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Pinterest pin.
trimNoWhen true, returns a smaller response with fewer fields.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond that: the tool only works for *public* pins, implying private/secret pins will not resolve. It says nothing about failure modes or response shape, so the addition is real 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, and the core operation is front-loaded before the input requirement. Nothing in the text is redundant or padded.

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 5-parameter tool with 3 required protocol parameters and no output schema, the description is adequate but incomplete: it never indicates what a returned pin contains or how `trim` changes the response. It leans entirely on the schema's 100% coverage, which is defensible but leaves the call outcome opaque.

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%, so the schema already explains url, trim, context, llm_model, and conversation_id in detail. The description only echoes the `url` requirement, adding no meaning beyond the schema, which lands it at the baseline 3.

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 gives a specific verb and resource ('Fetch a public Pinterest pin by URL'), and the 'by URL' qualifier distinguishes it from the search/list siblings such as pinterest_search_pins_list. It stops short of naming any sibling explicitly, so differentiation is implied rather than stated.

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 or when-not-to-use guidance, and no mention of the sibling tools (search or board listing) that would be the alternative for discovery-style lookups. 'Requires `url`' is a prerequisite restated from the required-parameters list, not usage guidance.

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