Playbook

Copy assets

copy_assets

Copy one or more assets into a target board. Accepts an array of asset tokens and the destination board token. Returns immediately (202 Accepted) — the copy runs asynchronously, so the new assets may take a few seconds to appear. Requires a token with the write scope.

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>",
      "collection_token": "<collection_token>"
    },
    "name": "copy_assets"
  }
}

Input Schema

Name	Required	Description
`asset_tokens`	Yes	Asset tokens to copy
`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.
`collection_token`	Yes	Destination board token

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

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

First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) it adds genuinely useful behavior: the call returns 202 immediately, work runs asynchronously, and new assets may take seconds to appear. It also discloses the write-scope auth requirement. It stops short of saying whether the source assets are left untouched or what happens on duplicate/name collisions.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose before the async caveat and the auth requirement. No sentence is redundant and nothing important is buried.

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?

With no output schema, the note that the call returns 202 rather than the created assets is exactly the missing piece an agent needs to avoid misreading the response. Three params at full schema coverage means the remaining burden on the description is small; only failure modes are unaddressed.

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 the schema already documents asset_tokens, collection_token, and the optional organization workspace fallback in detail. The description only restates the array-of-tokens and destination-board inputs without adding format, limits, or cross-field semantics.

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 first sentence gives a specific verb and resource ('Copy one or more assets into a target board'), which self-differentiates from the sibling move_assets by the copy-vs-move verb. It does not name that sibling explicitly, so the differentiation is implicit rather than stated.

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?

The description states a prerequisite ('Requires a token with the `write` scope') but never says when to choose this over move_assets, group_assets, or upload_from_urls, nor any when-not-to-use condition. Usage is inferable from the verb only.

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?