Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Resolve share link

resolve_share_link
Read-only

Turn a share link of the user's workspace (https://playbook.com/s/{workspace}/{link}) into the board behind it. Returns organization, board_token, board_title, uploads_enabled and expired. To read what is on the link, call list_assets with THAT organization (a full URL names its own workspace, which may not be your default), collection_token: board_token and nested_assets: true. Only active links of a workspace the user belongs to resolve; a link that shares hand-picked assets rather than a board is refused. A board's own address in the app (https://playbook.com/{workspace}/{board_token}, no /s/) is accepted too: it already carries the board token, and comes back as organization, board_token and board_title only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
share_urlYesThe full share URL, or just its last path segment. A full URL names its own workspace, so `organization` is not needed with one.
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / share_url / description
      Previous value: -"The full share URL, or just its last path segment"New value: +"The full share URL, or just its last path segment. A full URL names its own workspace, so `organization` is not needed with one."
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "share_url",
-  "context"
-]New value: +[
+  "share_url"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, but the description goes well beyond them: it enumerates the exact response fields, discloses that the /s/ form returns five fields while the plain board address returns only three, and describes authorization-like scope ('workspace the user belongs to') plus a refusal case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then the follow-up call, then the edge cases; every sentence carries operational information. The parenthetical asides and the trailing second-URL paragraph make it denser than it needs to be, but nothing is 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?

There is no output schema, so the description carries the return-value burden and does so by naming all five fields. Combined with the chaining instruction, the refusal case, and the alternate URL form, an agent has everything needed to call it and use the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: a full URL names its own workspace so `organization` is not needed with one, and `organization` may be omitted entirely for single-workspace accounts. It reinforces rather than merely restates the schema's parameter notes.

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+resource ('Turn a share link ... into the board behind it') and immediately enumerates the return fields, so an agent knows this is a resolver, not a reader. It also distinguishes itself from get_board and list_assets by naming the follow-up call needed to actually read content.

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?

Gives explicit routing: to read the link's contents, call list_assets with THAT organization, collection_token: board_token and nested_assets: true. It also states the exclusion conditions — only active links in a workspace the user belongs to resolve, and links sharing hand-picked assets rather than a board are refused.

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

All Playbook 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