Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get Pinterest pins, profiles and boards

get_pinterest_pins
Read-onlyIdempotent

Public Pinterest data from search words, profiles, boards or pin links: pins with image or video, title, description, outbound link, saves, comments, product name and price, pinner and board; profile details with followers and pin counts…

Instructions

Public Pinterest data from search words, profiles, boards or pin links: pins with image or video, title, description, outbound link, saves, comments, product name and price, pinner and board; profile details with followers and pin counts; boards. No login. Useful for trend and product research, creator discovery and visual content sourcing. Runs the Apify Actor tacps126/pinterest-scraper on your Apify account (about $0.0015 per pin, profile or board, $0.001 per search preview; spend per call is capped at $0.5).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pinterest_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoProfile, board or pin links, e.g. ["https://www.pinterest.com/nasa/"].
queriesNoSearch words, e.g. ["modern kitchen"].
max_itemsNoMaximum results to return (default 100, max 2000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
profiles_onlyNoOnly profile and board details, no pins.
include_boardsNoAlso list each profile's boards.
pins_per_sourceNoPins to read per search, profile or board.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds the material facts those annotations cannot: no login required, which Actor is executed on the user's account, per-item pricing (~$0.0015 per pin/profile/board, $0.001 per search preview) and a hard $0.5 per-call spend cap. Cost exposure is the single biggest behavioral risk for a paid scraping tool and it is disclosed with numbers.

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?

Front-loads the payload (what data, from which source types) then the operational facts (no login, Actor, cost). It is a dense single block rather than being broken up, but nearly every clause carries information an agent needs to select and safely invoke it; the cost sentence clearly earns its place.

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

Completeness5/5

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

For a 7-parameter, nested-object, paid scraping tool with an output schema present, the definition covers the selection criteria (source types), the payload summary, authentication posture, and cost ceiling. Nothing required to call it correctly is missing, and return-value structure is correctly left to the output schema.

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 one of the 7 parameters is already documented, and the cost note on max_items is already in the schema. The description reinforces the pricing model but adds no semantics about the interaction between links and queries, when to prefer profiles_only vs include_boards, or how pins_per_source composes with max_items. Baseline 3 is 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?

States specific verb and resource ('Public Pinterest data') and enumerates exactly what is returned per source type: pins with image/video, title, description, outbound link, saves, comments, product name/price, pinner/board; profile followers and pin counts; boards. The platform makes it trivially distinguishable from the sibling set, which covers Amazon, Facebook, YouTube, Trustpilot, etc.

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?

Gives concrete usage contexts — trend and product research, creator discovery, visual content sourcing — which tells the agent what class of question this tool answers. It stops short of explicit exclusions or 'use X instead of this' routing, which is the only thing separating it from a 5.

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