Skip to main content
Glama

Log out of Pinterest

pinterest_logout
Destructive

Deletes the locally stored Pinterest token to sign out of Pinterest and clear saved authentication from the local environment.

Instructions

Deletes the locally stored Pinterest token.

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_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The destructiveHint=true annotation already tells the agent the call is destructive, so the description's added value is the scope: only the *locally stored* token is deleted, implying the remote/server-side session is not revoked. That is exactly the right kind of context, but it omits failure behaviour (e.g. no token present) and whether re-authentication is required afterwards.

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?

A single nine-word sentence with the resource and effect front-loaded and zero filler. Nothing is redundant with the title beyond the unavoidable restatement of 'logout'.

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

Completeness3/5

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

Minimal but viable for a zero-parameter, no-output-schema tool whose destructiveness is already flagged by annotations. An agent still has to guess what happens when no token exists and whether the server-side session survives, which matters for deciding whether to follow up with pinterest_login.

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 and the schema is an empty object with 100% coverage, so there is no parameter meaning for the description to supply. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Deletes the locally stored Pinterest token.' An agent can tell this is the teardown counterpart of pinterest_login rather than a read like pinterest_auth_status. It stops short of 5 because it never explicitly contrasts itself with the login/auth-status siblings.

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?

There is no when-to-use, when-not-to-use, or alternative named in the description text. The only usage cue comes from the name and title ('log out'), which is implied rather than stated — the same gap that caps other thin mutation descriptions at 2.

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