Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

Check board access

check_board_access
Read-onlyIdempotent

Check whether an account can publish to a board right now, and why not.

    Use before publishing to a board not used recently, or after a publish
    failed with any board_* code, instead of retrying blind. For a
    full preflight of a specific pin use create_pin with dry_run=true.

    Returns publishable (bool), status (ok | failed | skipped when Pinterest
    was unreachable), code (board_not_found, board_not_owned, board_deleted,
    board_access_denied, scope_missing, token_expired), message, remediation,
    board, account_health, source (cache | pinterest). Never raises for a
    bad board; an unknown account fails with not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freshNotrue bypasses the cached verdict and asks Pinterest again.
board_idYesPinterest board ID (numeric string), from list_boards.
account_idYesUUID of a connected Pinterest account, from list_pinterest_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / account_id / description
      Added value: +"UUID of a connected Pinterest account, from list_pinterest_accounts."
    • addedInput schema / properties / board_id / description
      Added value: +"Pinterest board ID (numeric string), from list_boards."
    • addedInput schema / properties / fresh / description
      Added value: +"true bypasses the cached verdict and asks Pinterest again."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it readOnly, idempotent, and non-destructive; the description adds substantial behavioral detail: it returns a structured verdict, may be served from cache, skips when Pinterest is unreachable, never raises for a bad board, and fails with not_found only for unknown accounts. This goes well beyond annotation-only disclosure.

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 front-loaded with the core purpose, followed by clear usage guidance and a compact but valuable enumeration of return fields. Every sentence adds information, and the structure makes it easy for an agent to quickly identify what the tool does and when to use it.

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

Completeness5/5

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

For a read-only check tool with no output schema, the description covers purpose, when to use it, the alternative, return values, failure modes, cache behavior, and edge-case behavior. No critical information is missing for correct selection and 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 the schema already documents account_id, board_id, and fresh. The description adds context about the cache source and unknown-account failure, but does not significantly expand the meaning of the parameters themselves. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Check whether an account can publish to a board right now, and why not.' This clearly distinguishes it from sibling tools by framing it as a pre-publish access check rather than a publishing or board-management action.

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?

The description gives explicit usage conditions: use before publishing to a board not used recently, or after a publish fails with a board_* code. It also names the alternative (create_pin with dry_run=true) for a full pin-level preflight, making the decision boundary clear.

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

All pinbridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources