Playbook

Create asset version

create_asset_version

Destructive

Upload a file from a public URL as a NEW VERSION of an existing asset — the asset keeps its token, boards, and links, and its live bytes are REPLACED (head_version_number moves forward; the current head is snapshotted first). Requires a write-scope token and versioning enabled on the workspace plan. The URL must be a public https:// address (private/loopback/metadata hosts are refused). NOT idempotent — each call uploads fresh bytes and mints a new version even for an identical file, so on a timeout do NOT blind-retry; re-list versions with list_asset_versions to check whether it landed. v1 uploads a single request up to a size cap; files that need multipart upload on this workspace's storage (>=5MB on Backblaze) or exceed the cap are refused with an error directing you to the Playbook web or desktop app. The optional comment is recorded on the snapshot of the REPLACED head (not on the new content), matching revert.

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": {
      "token": "<token>",
      "uri": "<uri>"
    },
    "name": "create_asset_version"
  }
}

Input Schema

Name	Required	Description
`uri`	Yes	Public https:// URL of the new file's bytes
`title`	No	Filename used to derive extension/media type; defaults to the URL's last path segment
`token`	Yes	Token of the EXISTING asset to add a version to
`width`	No	Pixel width — only pass if actually known; do NOT guess. Omit and the server derives it.
`height`	No	Pixel height — only pass if actually known; do NOT guess. Omit and the server derives it.
`comment`	No	Optional note recorded on the snapshot of the REPLACED head (not the new content)
`media_type`	No	MIME type; defaults to the source response's Content-Type
`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: -[
-  "token",
-  "uri",
-  "context"
-]New value: +[
+  "token",
+  "uri"
+]

First observedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations (readOnly=false, destructive=true, idempotent=false) by explaining exactly what is destroyed and preserved: live bytes are REPLACED, head_version_number advances, the prior head is snapshotted, and token/boards/links survive. It also discloses auth scope, a plan-level precondition, host restrictions, size ceilings, and the non-idempotent timeout hazard with a recovery path.

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?

The core action is front-loaded in the first clause and every sentence carries distinct information (preservation, auth, host rules, retry hazard, size cap, comment semantics). It is dense and long for a single paragraph, with heavy parentheticals and caps that slightly tax scanning, 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?

For an 8-parameter destructive upload with no output schema, the description covers what is needed to call it correctly and to recover from failure: prerequisites, URL eligibility, size limits, the exact mutation semantics, and the verification tool. Nothing material is left to inference.

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 constraints the schema omits: only public https addresses are accepted and private/loopback/metadata hosts are refused. The `comment` clarification (recorded on the replaced head's snapshot, matching revert) largely restates the schema text, so the uplift is modest rather than decisive.

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 ('upload a file ... as a NEW VERSION of an existing asset') and immediately differentiates from the sibling `upload_from_url` by emphasizing that the target asset already exists and keeps its token. An agent can distinguish this from `upload_from_url`, `finish_upload`, and `update_asset` without opening any 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?

Explicitly gives when-to-use, when-not-to-use (files needing multipart, >=5MB on Backblaze, or above the cap are refused and must go to the web/desktop app), prerequisites (write scope, versioning on plan), and a concrete failure protocol ('do NOT blind-retry; re-list versions with list_asset_versions'). All alternatives and exclusions are named.

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?