Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_pinterest_boards

Read-onlyIdempotent

Retrieve a paginated list of Pinterest boards for the authenticated user, optionally filtered by public, protected, or secret privacy settings.

Instructions

List Pinterest boards for the authenticated user.

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

Input Schema

NameRequiredDescriptionDefault
privacyNoPUBLIC, PROTECTED, or SECRET
bookmarkNoPagination cursor
page_sizeNo
access_tokenNoPinterest access token (or set PINTEREST_ACCESS_TOKEN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. The description adds the useful auth context that results are scoped to the authenticated user, but it does not explain pagination behavior or what is returned.

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?

The description is a single front-loaded sentence with no wasted wording. It is appropriately concise for this simple list operation.

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?

For a simple read-only list tool with rich annotations, the description is minimally adequate. However, with no output schema, it could provide more context about returned board fields, pagination, or privacy filtering to help an agent invoke it confidently.

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 75%, so most parameters are documented in the schema. The description only adds the authenticated-user context and does not clarify the privacy filter, bookmark cursor, or undocumented page_size parameter, so it does not add much beyond the schema.

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: listing Pinterest boards. The scope is also clear: boards belonging to the authenticated user. It does not explicitly distinguish itself from nearby siblings such as get_pinterest_board or list_pinterest_pins, so it falls short of a 5.

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?

The description implies the basic use case but gives no explicit guidance on when to choose this tool over alternatives. It does not mention get_pinterest_board for a single board or list_pinterest_pins for pins, nor does it explain pagination or filtering selection.

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