Skip to main content
Glama

pinbridge

by io.pinbridge
OverviewDiscussionsAdmin

List related keywords

list_related_terms
Read-onlyIdempotent

Look up the search terms Pinterest associates with your seed keywords.

    Use while drafting the title and description for create_pin; it reads
    Pinterest's own suggestions. Not needed for publishing itself.

    Returns id, related_term_count and related_terms_list (term plus its
    related terms). Counts against the workspace's Pinterest read limit and
    fails with rate_limited (with retry_after_seconds) when it is spent, or
    not_found for an unknown account.

Input Schema

NameRequiredDescriptionDefault
termsYesOne seed term, a comma-separated string, or a list of terms.
account_idYesUUID of a connected Pinterest account, from list_pinterest_accounts.
exact_matchNotrue keeps only groups whose term exactly matches a seed.

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 / exact_match / description
      Added value: +"true keeps only groups whose term exactly matches a seed."
    • addedInput schema / properties / terms / description
      Added value: +"One seed term, a comma-separated string, or a list of terms."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses return fields, rate-limit consumption, and specific error behavior including rate_limited with retry_after_seconds and not_found for unknown accounts. This adds meaningful operational context for a read-only, open-world tool.

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 purpose, then usage, then return and error behavior. Each sentence adds operational value, and there is no redundant restatement of schema or annotations.

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 simple read-only lookup with no output schema, the description explains what is returned and which failures can occur. Combined with annotations covering safety and idempotency, an agent has enough information to invoke it 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?

Schema description coverage is 100%, so all three parameters are already documented in the input schema. The description reinforces that terms are seed keywords but does not add syntax or format details beyond the schema, so the 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: 'Look up the search terms Pinterest associates with your seed keywords.' It also clarifies the relationship to create_pin and says it is not needed for publishing, which helps distinguish it from publishing-oriented siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance ('Use while drafting the title and description for create_pin') and when-not guidance ('Not needed for publishing itself'). It does not explicitly name an alternative keyword-research tool, which keeps it short of a 5.

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