Playbook

Get asset previews

get_asset_previews

Read-only

Render one or more assets as images at a size you choose, and get a URL per asset. This is how you LOOK at Playbook assets: the display_url on an asset is the full-size render (5000px is normal), which is wasteful to fetch and too large for most vision models. Ask for 1024 wide and you get a 1024px image. The URLs are SHORT-LIVED — they die at the end of the next hour, so 1-2 hours depending on when you call. They suit fetching now or showing in the current reply; anything that must keep working later — a stored link, a document, a hand-off — needs get_asset_permalinks. A SIZE IS REQUIRED — pass width, height, or both; without one this would hand back the same full-size render you already have. IMAGES ONLY: it renders the asset's original file, so a video or a PDF comes back with a URL that will not load, and an asset with no file at all (a note, a colour swatch, a link) is listed under no_file_to_render rather than given a URL. Check media_type starts with image/ first. Tokens missing from the response entirely are under not_found — unknown, or not visible to this token. One render per token per call, so ask for the assets you actually need to see rather than a whole board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_tokens": "<asset_tokens>"
    },
    "name": "get_asset_previews"
  }
}

Input Schema

Name	Required	Description
`width`	No	Width in pixels. 1024 is plenty for a vision model; pass width alone to keep the aspect ratio
`format`	No	Output format. Omit to keep the original — pass jpeg when the consumer is picky about webp
`height`	No	Height in pixels
`asset_tokens`	Yes	Tokens of the IMAGE assets to render (max 100 per call)
`organization`	No	Workspace 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.

Changed3 schema fields changedNov 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / height / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / width / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 5, 2026

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: -[
-  "asset_tokens",
-  "context"
-]New value: +[
+  "asset_tokens"
+]

First observedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover read-only/non-destructive safety; the description adds the short-lived URL TTL (~1-2 hours), images-only rendering semantics with concrete failure modes (video/PDF URLs 'will not load'), and the `no_file_to_render` / `not_found` partitioning. That is substantial behavior disclosure beyond structured fields.

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-loads the core action and follows with constraints in rough priority order (size, lifetime, images-only, response buckets). Dense and largely waste-free, though the all-caps emphasis and a couple of parenthetical asides add length that could be trimmed.

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?

No output schema exists, and the description still explains the return shape: a URL per asset, plus the `no_file_to_render` and `not_found` buckets. Combined with the size requirement and TTL, an agent has everything needed to call it correctly and interpret 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 baseline is 3, but the description adds meaning the schema lacks: the schema lists only `asset_tokens` as required, while the description states a size is effectively mandatory and explains the consequence of omitting it (full-size render). It also conveys the per-token render economy, though it leaves `format` and `organization` to 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?

States a specific verb and resource ('render one or more assets as images at a size you choose, and get a URL per asset') and immediately frames its role versus the full-size `display_url` and versus siblings like get_asset_permalinks. An agent knows exactly what this returns without opening the schema.

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?

Explicit when-to-use ('this is how you LOOK at Playbook assets'), when-not-to-use ('anything that must keep working later ... needs get_asset_permalinks'), and a precondition ('Check `media_type` starts with `image/` first'). It even guides call sizing ('ask for the assets you actually need to see rather than a whole board').

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

All Playbook tools Inspect

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

Need Help?