Playbook

List assets

list_assets

Read-only

List assets in a Playbook workspace, optionally filtered to a specific board. Set nested_assets with a board token to include its entire subtree. Use cursor pagination for a stable full crawl/reconcile; it is not a change feed and does not report deletions. For 'what is new in this board since X', pass created_after with collection_token and nested_assets. Signed display URLs expire after about 24 hours; store permalink when a permanent URL is required. Set uploaded_by to list everything one person added — prefer this over the search tools when you want a COMPLETE list, since it walks the database directly and is not subject to the search engine's result ceiling. Resolve the person with list_members first.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-indexed)
`cursor`	No	Use stable cursor pagination for a full crawl instead of page numbers
`fields`	No	Return ONLY these fields on each row. `token` is always included. Valid names: token, title, media_type, text_type, status, approved, approved_after, tags, permalink, display_url, stream_url, collection_token, size, is_skeleton, uploaded_by, source_error, ai_generated, ai_agent_payload. Use it when scanning a large board: `display_url` and `permalink` are ~400 characters each, so a 100-row page is mostly URL unless you narrow it. An unknown name is refused, not ignored: there is no `created_at`, `updated_at`, `width` or `height` among them, and an asset's dimensions come from get_asset or get_assets instead.
`per_page`	No	Items per page (1-100, default 20)
`uploaded_by`	No	List only assets uploaded by this person. Pass a member token from list_members. A name is accepted as a fallback and resolved server-side, but only when it matches exactly one member — otherwise the call fails and lists the candidates. One person per call; use search_assets or ai_search to filter by several at once.
`after_cursor`	No	Opaque cursor returned by the previous cursor-paginated response
`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.
`created_after`	No	Only assets uploaded strictly after this ISO 8601 timestamp or date (a bare date is midnight UTC). Sees NEW uploads only: an asset edited, retagged or moved into the board later keeps its original upload time and is not returned, and neither is an upload that auto-grouping stacked into a group that already existed. An unparseable value is refused.
`nested_assets`	No	Include assets from the board's entire nested subtree. Requires `collection_token` — on its own, with no board token, it is refused.
`get_ai_payload`	No	Include each asset's `ai_agent_payload` on the rows. Default false, and the key is then ABSENT rather than null, so you can tell 'I did not ask' from 'nothing is stored'. Each payload can be up to 4 KB, so a full page with this on is a large response — ask for it when you actually need the context, not by default. get_asset always returns it.
`collection_token`	No	Board token to filter by — the parameter name is `collection_token`, not `board_token`. Take the token from list_boards, list_board_children or ai_search: the id in a shared board link, a published page URL or a permalink is a different identifier, and passing one here fails the same way as a token from another workspace. A share link goes through resolve_share_link first, which returns the board token.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / collection_token / description

Previous value: -"Board token to filter by — the parameter name is `collection_token`, not `board_token`. Take the token from list_boards, list_board_children or ai_search: the id in a shared board link, a published page URL or a permalink is a different identifier, and passing one here fails the same way as a token from another workspace."New value: +"Board token to filter by — the parameter name is `collection_token`, not `board_token`. Take the token from list_boards, list_board_children or ai_search: the id in a shared board link, a published page URL or a permalink is a different identifier, and passing one here fails the same way as a token from another workspace. A share link goes through resolve_share_link first, which returns the board token."

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"
-}

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

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 already establish read-only/no-destroy, so the description is free to add the non-obvious behaviors: cursor pagination is not a change feed and does not report deletions, signed display URLs expire in ~24h so permalink should be stored, `ai_agent_payload` is absent rather than null when not requested, and `created_after` ignores later edits/retags/moves. These are exactly the traits an agent cannot infer from schema or annotations.

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 purpose and then organized by task (filtering, pagination, freshness, URLs, per-uploader). It is dense and slightly long at roughly six sentences, but each one carries distinct operational guidance rather than 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 read-only listing tool with no output schema, the description covers the gaps that matter: pagination model and its limitations, URL expiry, absence-vs-null semantics, failure modes for bad tokens/names, and how to select the right alternative tool. Nothing an agent needs to call it correctly appears to be missing.

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% and the per-field descriptions already carry most parameter detail, so the baseline is 3. The description adds integrative meaning beyond individual fields by binding parameters into workflows — 'for what is new in this board since X, pass created_after with collection_token and nested_assets' — and by reiterating the complete-list rationale for uploaded_by.

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?

Opens with a specific verb+resource+scope: 'List assets in a Playbook workspace, optionally filtered to a specific board.' It also distinguishes the tool from siblings by noting it should be preferred over the search tools when a complete list is needed, since it walks the database directly rather than going through the search index.

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 recipes: cursor pagination for a stable crawl/reconcile, `created_after` + `collection_token` + `nested_assets` for 'what is new since X', and `uploaded_by` for a complete per-person list with the alternative (search_assets/ai_search) named for multi-person filtering. It also states prerequisites (resolve the person with list_members, resolve share links via resolve_share_link).

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?