Skip to main content
Glama
Sign In
Pinterest MCP Server

Pinterest MCP Server

by Kargatharaakash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

pinterest_search_and_download

Search Pinterest images by keyword and download them directly to your device.

Instructions

Search for images on Pinterest by keyword and download them

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": {
      "keyword": "<keyword>"
    },
    "name": "pinterest_search_and_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of images to return and download (default: 10)
keywordYesSearch keyword
headlessNoWhether to use headless browser mode (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It omits details like download location, file format, browser automation implications (headless parameter not mentioned), and potential side effects.

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?

A single sentence with no wasted words, but it lacks front-loading of critical context. Appropriate length for the content provided.

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

Completeness2/5

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

With 3 parameters and no output schema, the description fails to explain return behavior (e.g., saved files, temporary storage) or how 'download' works. Incomplete for proper tool invocation.

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%, so baseline is 3. The description adds no additional meaning beyond what is already in the schema for parameters.

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 states the verb 'Search' and 'download', the resource 'images on Pinterest', and the method 'by keyword'. It distinguishes from sibling 'pinterest_search' by adding download functionality.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'pinterest_search' or 'pinterest_get_image_info'. The agent is left to infer usage from the name alone.

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