Retrieve a Pinterest pin's full public details, including title, description, image, board, pinner, comment and save counts, and creation time from its pin ID.
Get a Pinterest pin's full detail. Returns a single Pinterest pin's full detail: title, description, image, board, pinner, comment count, save count, and creation time. Public data sourced from Pinterest's own pin pages.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Pinterest pin id |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It notes the data is public and lists return fields, but does not address rate limits, authentication, or edge cases, giving moderate transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and front-loaded, but slightly redundant with 'full detail' repeated in both sentences. Overall it is efficient and no irrelevant content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description lists the key return fields, making it largely adequate for a simple lookup tool. It could mention error handling, but for this complexity it is complete enough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully documents the 'id' parameter (100% coverage), so the baseline is 3. The description adds no extra param details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get a Pinterest pin's full detail' and enumerates specific fields (title, description, image, board, pinner, comment count, save count, creation time), distinguishing it from sibling tools like pinterest_search or pinterest_user.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context implies usage when a specific pin ID is known, but it does not explicitly mention when to use alternatives or when not to use this tool, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.