Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Move assets

move_assets
DestructiveIdempotent

Move one or more assets to a target board. Accepts an array of asset tokens and the destination board token. Requires a token with the write scope. The caller must have update permission on every source asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_tokensYesAsset tokens to move
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.
collection_tokenYesDestination board token

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: -[
-  "asset_tokens",
-  "collection_token",
-  "context"
-]New value: +[
+  "asset_tokens",
+  "collection_token"
+]
  2. 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 destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation/safety profile is covered. The description adds value the annotations do not carry: the required `write` scope and the per-asset update permission on every source asset, which is exactly the kind of auth precondition an agent needs. It does not explain what happens to the source board listing, but that is largely implied by 'move'.

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?

Three short sentences, purpose front-loaded, then parameters, then permission constraints — well structured. The middle sentence partially duplicates what the 100%-covered schema already states, so it is not perfectly waste-free.

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?

For a 3-parameter tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the missing auth/permission layer. An agent has enough to invoke correctly; only return/error behavior is unspecified, which is acceptable given no output schema.

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%, including a detailed note on the optional `organization` parameter, so the schema carries the semantic load. The description restates the asset-token array and destination board token without adding format, ordering, or limit details beyond the schema.

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?

States a specific verb ('Move') and resource ('assets') plus the destination ('target board'). It is clearly distinguishable from copy_assets and move_page_element by verb alone, though it does not explicitly name those siblings.

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?

It gives real prerequisites (write scope token, update permission on every source asset) which implies when the call will succeed. However it offers no guidance on when to prefer this over copy_assets or how it differs from moving a page element — the alternative-selection dimension is left to inference.

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