AIsa Pinterest

get_pinterest_pin

Read-onlyIdempotent

Fetches one pin by URL, of the form pinterest.com/pin/. The response is a different shape from search results: camelCase fields including entityId, description, category, totalReactionCount, aggregatedPinData, richMetadata, pinner, originPinner and genAiTopics. Measured at 12.5 KB, the smallest full response in this API; trim=true reduces it to 1.6 KB, keeping entityId, description, createdAt, pinner, originPinner, nativeCreator, shareCount, repinCount and totalReactionCount while dropping richMetadata and category. To find pins by keyword use get_pinterest_search; to page through the board a pin sits on use get_pinterest_board. Only standard numeric pin URLs resolve: of 12 search results fed straight back, the 3 whose URL ended in a shortcode (dwA0UYrl style) all answered 404 and one numeric id did too, so check for a numeric trailing id before calling and expect occasional 404s on deleted pins.

Usage-based billing; Default request estimate: $0.00188 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`url`	No	Pinterest pin URL
`trim`	No	Set to true for a trimmed down version of the response
`cache_max_age`	No	If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / cache_max_age

Added value: +{
+  "description": "If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with \"cached\": true and a \"cached_at\" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching)",
+  "enum": [
+    "14d",
+    "1d",
+    "30d",
+    "3d",
+    "7d"
+  ],
+  "type": "string"
+}

addedInput schema / properties / trim / description

Added value: +"Set to true for a trimmed down version of the response"

addedInput schema / properties / url / description
```
Added value: +"Pinterest pin URL"
```

Changed6 schema fields changedOct 15, 2026
- removedInput schema / properties / trim / description
```
Removed value: -"Set to true for a trimmed down version of the response"
```
- removedInput schema / properties / trim / example
```
Removed value: -"false"
```
- changedInput schema / properties / trim / type
```
Previous value: -"boolean"New value: +"string"
```
- removedInput schema / properties / url / description
```
Removed value: -"Pinterest pin URL"
```
- removedInput schema / properties / url / example
```
Removed value: -"https://www.pinterest.com/pin/1124351863225567517/"
```
- changedInput schema / required
```
Previous value: -[
-  "url"
-]New value: +[]
```
Changed2 schema fields changedSep 18, 2026
- addedInput schema / properties / trim / example
```
Added value: +"false"
```
- addedInput schema / properties / url / example
```
Added value: +"https://www.pinterest.com/pin/1124351863225567517/"
```
First observedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: response size (12.5 KB), what trim actually changes (drops richMetadata and category, keeps a named field set), how shortcode URLs fail with 404, and the caching behavior's cost implications. This is unusually rich disclosure for a read tool.

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-loaded with purpose, then alternatives, then output-shape detail — a sensible ordering. It is dense and the long field enumeration plus the embedded pricing note add bulk, but nearly every sentence carries decision-relevant information, so it stays efficient rather than padded.

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?

An output schema exists, so return values need not be described, yet the description still quantifies size and the trim trade-off that the schema cannot express. Combined with the 404 and URL-format warnings, an agent has everything needed to call this 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 100%, so the baseline is 3, but the description adds real meaning: the exact URL shape pinterest.com/pin/<id> and a precise account of what trim trades away, which is more than the schema's vague 'trimmed down version'. cache_max_age semantics remain schema-only, keeping this just short of a 5.

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 (fetches) and resource (one pin) scoped by URL form, and explicitly distinguishes itself from get_pinterest_search and get_pinterest_board. An agent can route between the three pin/board/search tools without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit alternatives and the condition selecting each: 'To find pins by keyword use get_pinterest_search; to page through the board a pin sits on use get_pinterest_board.' It also adds a pre-call check (ensure a numeric trailing id) and a caveat to expect occasional 404s, which is actionable when-to-use guidance.

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

All AIsa Pinterest 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?