Skip to main content
Glama
subimpact

subimpact-data-mcp

Official

pinterest

Scrape pins from keyword searches, boards, or profiles to collect full-resolution images, videos, board details, and repin counts without login or API keys.

Instructions

Pinterest Scraper — Search, Boards & Profiles

Scrape Pinterest pins from keyword search, boards and profiles. Full-res originals, video variants, board/pinner metadata, repin counts. Pure HTTP - no browser, no login, no API key, no proxy.

Pricing (pay per event, billed to your Apify account): Pin scraped: $0.00199; Media downloaded: $0.005; platform usage billed to your account.

Runs on Apify as subimpact/pinterest-scraper.

Input Schema

NameRequiredDescriptionDefault
modeYessearch = keyword search (use queries). board = every pin on a board (use boardUrls or boardIds). profile = every pin a user has published (use usernames).search
queriesNoComma-separated search keywords, e.g. `ai wallpaper, minimal interior`. Required when mode=search — leave empty to use the default query `ai wallpaper`. NOTE: Pinterest's search payload contains images only — no title, description, board or pinner. Turn on "Enrich pin details" if you need those fields.ai wallpaper
boardIdsNoComma-separated numeric board ids, e.g. `286612032474627954`. Faster than boardUrls (skips the id-resolution request). Used when mode=board.
_maxItemsNoHow many dataset items to return to the model (1-1000, default 50). Truncates the response only; it does not change what the Actor collects or charges for.
boardUrlsNoComma-separated board URLs or paths, e.g. `https://www.pinterest.com/les_bons_details/interior-design/` or `/les_bons_details/interior-design/`. The numeric board id is resolved automatically from the board page. Used when mode=board.
imageSizeNoWhich image variant to put in `imageUrl` (and to download when media download is on). `orig` is the full-resolution original.orig
usernamesNoComma-separated Pinterest usernames, e.g. `ohuhu, nasa`. A leading @ and full profile URLs are accepted. Required when mode=profile.
includeRawNoKeep the untouched Pinterest pin object in the `raw` column. Turn off for smaller datasets.
maxPinsTotalNoOptional global cap across EVERY query / board / profile in the run, on top of max pins per source. Leave empty for no global cap (unlimited). Use this to keep long multi-source runs inside the 1-hour platform timeout.
_maxChargeUsdNoPer-run spending cap in USD (default 0.5). Passed to Apify as the run option maxTotalChargeUsd, so the run stops when it reaches this charge.
downloadMediaNoDownload each pin's image (or MP4 for video pins) into the run's key-value store and link it from the dataset row. Billed per file downloaded. Off by default — the image URLs in the dataset are directly usable.
enrichDetailsNoFetch each pin's detail endpoint for extra fields. Costs one extra HTTP request per pin, so runs take noticeably longer. Worth it in search mode; usually redundant in board/profile mode, where pins already arrive with full metadata. Without a login, the detail endpoint returns a reduced field set (SEO title/description, creator) — not the complete pin record.
maxPinsPerSourceNoMaximum pins to collect per query / board / profile. This is your cost ceiling: pins scraped × the per-pin price. Hard cap: 5000.
proxyConfigurationNoNot required — Pinterest's resource API responds normally to datacenter IPs. Kept as an escape hatch in case an exit IP gets throttled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the HTTP-only/no-login/no-proxy access model, output content such as full-res images, video variants, board/pinner metadata and repin counts, and per-event pricing. It does not cover rate limiting, failure modes, or full dataset structure, but the core operational traits are present.

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 front-loaded with what the tool does, then layers in key operational traits and pricing without padding. Every sentence contributes useful selection or cost information.

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 complex 14-parameter scraper with no annotations and no output schema, the description supplies the essential context: access model, billing, and the kinds of data returned. Detailed parameter behavior is covered by the very rich schema, though the description stops short of fully describing the output dataset shape.

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 documents all 14 parameters in detail. The description adds high-level context about the supported modes and billing model but does not add parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource — scraping Pinterest pins — and names the three supported modes: keyword search, boards, and profiles. The Pinterest focus clearly distinguishes it from the other social/scraping siblings such as tiktok_hashtag or youtube.

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 implies the tool is for Pinterest pin scraping across search, boards, and profiles, but it does not explicitly say when to choose this over alternatives or when not to use it. Mode selection guidance lives in the schema rather than the description.

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