Skip to main content
Glama
Sign In
dev.socialscrape/socialscrape

dev.socialscrape/socialscrape

Official
by SocialScraper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Pinterest

pinterest
Read-onlyIdempotent

Fetch board pins, individual pins, user boards, search results, and topic pins by selecting a resource and passing a URL, query, or handle; supports cursor pagination and cached responses.

Instructions

Data from Pinterest: posts and videos, collections.

Pick a resource, then pass its parameters as top-level arguments (extras in params). Each call costs the credits shown below and the result says what was charged and what is left; failures are free. List resources return a cursor: pass it back unchanged for the next page. Pass max_age_days to accept a cached copy for free.

Resources:

  • board(url): Pinterest board pins. 1 credit. Paged.

  • pin(url): Pinterest pin. 1 credit.

  • profile.boards(handle): Pinterest user boards. 1 credit. Paged.

  • search(query): Pinterest pin search. 1 credit. Paged.

  • topic(url): Pinterest topic pins. 1 credit. Paged.

Input Schema

NameRequiredDescriptionDefault
urlNoURL of the item the resource is about (profile, post, video, event...). Used by: board, pin, topic
queryNoSearch terms. Used by: search
cursorNoOpaque cursor from the previous page; pass it back unchanged
handleNoUsername, with or without the leading @. Used by: profile.boards
paramsNoAny other parameter for the chosen resource, by name, e.g. {"start_date": "2026-01-01"}. Optional parameters of each resource are in the tool description; call describe for types and allowed values.
resourceYesWhich Pinterest data to fetch. The tool description lists what each needs.
max_age_daysNoAccept a cached copy fetched within this many days, for 0 credits (0 to 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses that each call costs credits, failures are free, the result reports charged and remaining credits, list resources are paged via cursor, and max_age_days can return a cached copy for free. These are meaningful operational behaviors that materially affect invocation.

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?

The description is compact and front-loaded: purpose first, then invocation rules, then the resource list with costs and paging notes. Every section earns its place for a multi-resource tool with credit and pagination semantics.

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 five-resource proxy tool, it covers the required invocation pattern, costs, caching, pagination, and each resource's key parameter. The main gap is that it does not enumerate optional resource parameters and relies on describe for those details, but the overall definition is sufficient to call the tool correctly.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds useful mapping by listing which parameter each resource needs, such as board(url), search(query), and profile.boards(handle). It also clarifies that resource-specific extras go in params, though it does not fully document those optional parameters itself.

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

Purpose5/5

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

The description clearly scopes the tool to Pinterest data and enumerates the exact resource types it can fetch: board, pin, profile.boards, search, and topic. This distinguishes it from sibling platform tools such as youtube, tiktok, and instagram without requiring the schema to be opened.

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

Usage Guidelines4/5

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

It explains how to use the resource parameter and pass parameters, and it gives credit costs plus pagination behavior. It does not explicitly state when to choose this over sibling tools or when not to use it, but the Pinterest scope makes the intended usage clear.

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