Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

Get scheduled pin

get_schedule
Read-onlyIdempotent

Fetch one scheduled pin (a pin queued to publish at a future time) by id.

    Use to check whether a schedule is still pending, has published, failed
    or was canceled. To browse schedules use list_schedules; once status is
    done, follow the resulting pin with get_pin using pin_id.

    Returns the schedule with status, run_at, pinterest_account_id, payload
    (board_id, title, media), pin_id and last_error. An unknown id fails
    with not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idYesUUID of the schedule, from list_schedules or create_schedule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / schedule_id / description
      Added value: +"UUID of the schedule, from list_schedules or create_schedule."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only/idempotent/non-destructive annotations, the description reveals the exact return shape ('status, run_at, pinterest_account_id, payload ... pin_id and last_error') and failure behavior ('An unknown id fails with not_found'). Since there is no output schema, this behavioral disclosure is especially valuable.

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 action, then gives usage context, alternatives, return details, and error semantics in compact, purposeful sentences. No sentence is redundant or 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?

For a single-parameter read-only retrieval tool, the description covers what the tool does, when to use it, what it returns, how to act on the result, and what happens on a bad id. With no output schema, this is fully sufficient for an agent to invoke and interpret the call correctly.

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?

The schema already provides 100% coverage for schedule_id, including its UUID type and provenance ('from list_schedules or create_schedule'). The description adds only the generic 'by id', so it does not meaningfully improve on the schema.

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 uses a specific verb and resource: 'Fetch one scheduled pin ... by id' and defines what a scheduled pin is. It clearly distinguishes this tool from list_schedules and get_pin, matching its place among the sibling tools.

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?

It explicitly states when to use the tool ('check whether a schedule is still pending, has published, failed or was canceled') and routes to alternatives: 'To browse schedules use list_schedules' and 'follow the resulting pin with get_pin using pin_id.' This gives an agent unambiguous selection criteria.

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