SiteCheck Shop & Social

Latest pins of a public Pinterest profile from Pinterest's

social_pinterest

Read-only

Latest pins of a public Pinterest profile from Pinterest's own RSS feed: profile name and description, and for each of the newest 25 pins the pin URL and ID, text, image URL and publish date. Works for public profiles without login; boards, search and engagement counts are not part of the feed. Related tools on this server, for a different need: social_snapchat when you need Public Snapchat profile from its web profile page; social_truthsocial when you need Truth Social account and its latest posts: profile and up. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "username": "<username>"
    },
    "name": "social_pinterest"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Pins to return, 1 to 25 (default 25)
`username`	Yes	Pinterest username, e.g. nasa (from pinterest.com/<username>/)

Output Schema

Name	Required	Description	Default
`pins`	No
`source`	No
`profile`	No
`username`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the data source (RSS feed), the no-login requirement, the 25-pin ceiling, and the billing model ($0.002 per successful call via x402, failures not charged). It does not describe error behavior for private/nonexistent profiles, but the cost and access constraints are the high-value disclosures here.

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?

Purpose and return contents are front-loaded in the first clause, with constraints and pricing following. The 'Related tools on this server, for a different need' boilerplate adds bulk without helping selection, but nothing is genuinely wasted elsewhere.

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?

With an output schema present and annotations covering safety, the description fills in the remaining operational context: source, login requirement, coverage limits, and cost. Only failure modes (private/renamed accounts) are left unspecified, a minor gap for a read-only fetch tool.

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 coverage is 100% and both parameters are self-documenting, so the baseline of 3 applies. The description reinforces the 25-pin maximum but adds no syntax or format detail beyond what the schema already states.

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 a specific verb and resource ('Latest pins of a public Pinterest profile') plus the data source ('Pinterest's own RSS feed') and enumerates the returned fields (URL, ID, text, image URL, publish date). The agent can distinguish it from other social_* siblings without opening the schema.

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 clear preconditions ('Works for public profiles without login') and explicit exclusions ('boards, search and engagement counts are not part of the feed'), which tell the agent when not to call it. The sibling mentions (snapchat, truthsocial) are cross-platform pointers rather than true alternatives for the same need, so routing guidance is partial.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?