Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

List Pinterest accounts

list_pinterest_accounts
Read-onlyIdempotent

List the Pinterest accounts connected to this workspace with their health.

    Use first: list_boards, create_pin, create_schedule and get_rate_meter
    all need an account_id from here. Also read pinbridge://accounts. To
    connect a new account or fix reconnect_required, the user must use the
    PinBridge dashboard; there is no tool for that.

    Returns {"items": [...], "connect_url": "...", "next_step": ...}. items has
    one entry per account with id (the account_id), username, display_name,
    scopes (comma-separated), token_expires_at and health: health_status
    (healthy, refresh_due, reconnect_required or scope_missing),
    health_message, reconnect_required and missing_scopes. connect_url opens
    the dashboard's connect step. When items is empty nothing is connected:
    next_step says to give the user connect_url. Accounts outside this API
    key's allow-list are omitted. Never fails for a valid key.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_pinterest_accountsOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and non-open-world behavior. The description adds substantial context beyond annotations: health_status values, token_expires_at, connect_url, next_step behavior for empty items, allow-list omissions, and the guarantee that it never fails for a valid key.

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?

Front-loads the core purpose and health scope, then explains usage and return structure. Every sentence adds operational value, including the dashboard limitation and empty-account handling, with no redundant filler.

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?

Although there is no output schema, the description fully documents the return shape: items fields, health states, connect_url, next_step, and empty-list behavior. It also covers prerequisites, limitations, and non-failure guarantees, making it complete for an agent to call and interpret the tool correctly.

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 the baseline is 4. The description appropriately focuses on returned account fields and does not need to explain input parameter semantics.

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: list Pinterest accounts connected to this workspace, including their health. It clearly distinguishes this from the many other list_* tools by scoping to connected accounts and health status.

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?

Explicitly says to use this first because list_boards, create_pin, create_schedule and get_rate_meter all need an account_id from here. It also directs the agent to the pinbridge://accounts resource and explains that connecting or fixing reconnect_required must happen in the PinBridge dashboard because no tool exists for it.

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