Skip to main content
Glama

Log in to Pinterest

pinterest_login

Starts Pinterest OAuth login to access your private or secret boards and search; opens the consent page and returns a URL to check approval status if needed.

Instructions

Starts the official Pinterest OAuth login (needed only for the user's own private/secret boards and search; public boards work without it via get_public_board). Opens the Pinterest consent page in the browser and waits briefly for approval. If approval takes longer, returns the URL; call pinterest_auth_status afterwards.

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": "pinterest_login"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does most of it: it discloses the browser/consent-page side effect, that it blocks only briefly, that it may return a URL instead of completing, and which sibling to poll next. It stops short of saying whether the token persists across calls or what a repeat invocation does to an existing session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and its scope, then the fallback behavior. Every clause adds information an agent needs; nothing is repeated from the schema or title.

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?

For a zero-param auth tool with no output schema and no annotations, the description covers the trigger, the side effect, the asynchronous escape hatch, and the follow-up tool. The only real gap is post-success state, such as whether a session is now active and whether re-login is needed later.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline credit applies. The description correctly signals a no-argument call by describing a flow rather than any inputs.

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 ('Starts the official Pinterest OAuth login') and immediately scopes it: needed only for the user's own private/secret boards and search. It explicitly contrasts with the sibling get_public_board, so an agent can pick between them without opening either 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 when-needed (private/secret boards and search), when-not-needed (public boards work without it via get_public_board), and the follow-up path if approval stalls (call pinterest_auth_status afterwards). Both the alternative tool and its selecting condition are named.

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