Playbook

Ungroup assets

ungroup_assets

Destructive

Pull assets out of the group they belong to, leaving them as standalone assets on the board. A group is a container asset that holds other assets as variants — different formats or crops of the same thing, or a set of colour swatches, which Playbook shows as a palette. The group has no file of its own and takes its preview from its first displayable child. Requires a token with the write scope. Every token must name an asset that is currently inside a group — one that is not makes the whole call fail. IMPORTANT: a group left with fewer than two assets is dissolved — its last asset is freed too and the group asset is deleted. So ungrouping one member of a two-member group frees both, and the returned list names only the assets you asked for, not every asset that changed. Re-read the group with get_asset if you need its current state.

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": {
      "child_asset_tokens": "<child_asset_tokens>"
    },
    "name": "ungroup_assets"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`child_asset_tokens`	Yes	Tokens of the grouped assets to pull out

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

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations it discloses the non-obvious destructive side effect that a group left with fewer than two assets is dissolved and its last asset freed, and warns that the returned list names only requested assets, not everything changed. It also names the required `write` token scope, which no annotation conveys.

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 action and its warning are front-loaded, and the sentences carry distinct information (definition, auth, preconditions, dissolution caveat). The middle explanation of what a group is and how its preview is derived is useful but slightly longer than strictly needed for invocation.

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?

With only two parameters, no output schema, and a genuinely surprising destructive side effect, the description covers everything an agent must know: scope requirement, per-token precondition, dissolution behavior, and what the return value does and does not include.

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 the baseline is 3, but the description adds real constraint semantics for child_asset_tokens — each token must name a currently grouped asset or the call fails — which the schema's one-line item description does not state. The `organization` parameter is left entirely 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?

The description opens with a specific verb and resource ('Pull assets out of the group') and immediately contrasts with its sibling by defining what a group is versus a standalone asset, so an agent can distinguish ungroup_assets from group_assets without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear preconditions and failure modes: every token must currently be inside a group or the whole call fails, and it points to get_asset when current state is needed. It stops short of naming group_assets as the inverse operation or stating when ungrouping is preferable to moving or deleting assets.

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?