Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Pinterest profile boards

pinterest_profile_boards_list
Read-onlyIdempotent

List public boards for a Pinterest profile by handle, returning paginated results with a cursor for retrieving additional boards.

Instructions

List public boards for a Pinterest profile. Requires handle. 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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "pinterest_profile_boards_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, returns a smaller response with fewer fields.
cursorNoOpaque pagination cursor returned by a previous response.
handleYesRequired. Pinterest username whose boards should be listed.
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, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds genuinely new context by scoping results to public boards only and pointing at cursor-based pagination, but says nothing about rate limits, empty results, or auth requirements.

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?

Three short sentences, front-loaded with the resource scope before the prerequisite and pagination note. Nothing is redundant, though the parenthetical pagination aside is slightly terse.

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

Completeness4/5

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

For a simple read-only list tool with a fully described schema and rich annotations, this is close to sufficient: scope, prerequisite and pagination are all covered. The meta-parameters (context, llm_model, conversation_id) are fully documented in the schema, so the description needn't repeat them.

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 including handle, cursor, trim, context, llm_model and conversation_id is already documented in the schema. The description restates the handle requirement and cursor purpose without adding syntax or edge-case meaning, so baseline 3 applies.

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?

States a specific verb and resource ('List public boards for a Pinterest profile'), which lets an agent separate it from siblings like pinterest_board_pins_list or pinterest_search_pins_list. It doesn't name those alternatives explicitly, so it falls just short of full sibling differentiation.

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?

'Requires `handle`' gives a prerequisite, and 'use cursor when paginated' implies follow-up calls, but there is no explicit statement of when to use this versus listing pins or searching pins. Usage is implied rather than directed.

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