Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Pinterest pins

pinterest_search_pins_list
Read-onlyIdempotent

Search public Pinterest pins by keyword and return a paginated list for research or content discovery.

Instructions

Search public Pinterest pins by keyword. Requires query. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "pinterest_search_pins_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, returns a smaller response with fewer fields.
queryYesRequired. Search query text for Pinterest pins.
cursorNoOpaque pagination cursor returned by a previous response.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that results are public-only and that responses may be paginated, but says nothing about result-count limits, rate limiting, or the conversation_id sequencing requirement that shapes how calls must be issued.

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 with zero filler, leading with the core verb+resource and following with the required-parameter and pagination notes. Nothing is repeated and nothing is 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 six-parameter search tool with three required parameters and no output schema, the description covers only the query and cursor aspects. The mandatory context, llm_model and conversation_id handshake parameters — the most error-prone part of invoking this tool — are left entirely to the schema, and the return shape is described only as "a list".

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 every parameter is already documented in the schema; the baseline is 3. The description restates that query is required and gestures at cursor pagination, adding no format, bounds, or semantics beyond the schema, and it ignores the trim and analytics parameters entirely.

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?

"Search public Pinterest pins by keyword" gives a specific verb (search) plus resource (public Pinterest pins) and a mechanism (keyword), which implicitly separates it from board- or profile-scoped siblings like pinterest_board_pins_list. It stops short of naming any alternative explicitly, so an agent must infer the boundary rather than being told it.

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 description states the precondition ("Requires `query`") and the pagination follow-up ("use cursor when paginated"), which is useful operational guidance. However, it never says when to prefer this over pinterest_board_pins_list or pinterest_pin_get, nor any exclusion such as private pins being unreachable.

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