Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Get board

get_board
Read-only

Get details of a specific board by its token. Returns the board's title, description, asset count, parent board, and child board count. published_page says whether the board's public page is live (active), its url (null unless live) and the template its page design uses (can be set on a page that is not live). asset_count covers the board AND every board nested under it (each group/stack counted once); list_assets on a board returns only assets sitting directly on it unless you pass nested_assets: true, so compare the count against that, not the plain listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesBoard token, as returned by list_boards, list_board_children or ai_search — the parameter name is `token`, not `board_token`. The id in a share link (`/s/{workspace}/{id}`) is NOT a board token: pass the link to resolve_share_link, which returns the board. Nothing converts a published page URL: look that board up by title with list_boards `query` or ai_search instead of taking an id out of a URL, a spreadsheet or an earlier session.
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 / token / description
      Previous value: -"Board token, as returned by list_boards, list_board_children or ai_search — the parameter name is `token`, not `board_token`. The id in a shared board link or a published page URL is NOT a board token and nothing converts one: look the board up by title with list_boards `query` or ai_search instead of taking an id out of a URL, a spreadsheet or an earlier session."New value: +"Board token, as returned by list_boards, list_board_children or ai_search — the parameter name is `token`, not `board_token`. The id in a share link (`/s/{workspace}/{id}`) is NOT a board token: pass the link to resolve_share_link, which returns the board. Nothing converts a published page URL: look that board up by title with list_boards `query` or ai_search instead of taking an id out of a URL, a spreadsheet or an earlier session."
  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: -[
-  "token",
-  "context"
-]New value: +[
+  "token"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, so the safety profile is covered. The description goes beyond that by disclosing semantics an agent could not infer: asset_count includes nested boards (each group/stack counted once), published_page url is null unless live, and template can be set on a non-live page. That is real added behavioral context.

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 core purpose, then the return-field semantics in a compact block. Every sentence carries information, though the asset_count/list_assets sentence is dense and slightly long-winded.

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

Completeness4/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 must describe the return shape — and it does, naming title, description, asset_count, parent board, child board count and published_page sub-fields. Complete enough for a two-parameter read tool; only the child/parent field formats remain unspecified.

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 token and organization are already fully documented (including the token-vs-share-link trap and workspace omission rule). The description only repeats 'by its token' and adds no format or edge-case guidance beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Get details of a specific board by its token') and enumerates exactly which fields come back. This distinguishes it from list_boards/list_board_children, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: there is no 'use this when you already have a token' or 'to enumerate boards use list_boards instead'. It does give one actionable comparison rule (asset_count vs list_assets without nested_assets), but no when/when-not framing against the many sibling read tools.

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