Playbook

Move page element

move_page_element

DestructiveIdempotent

Move an element to another position, another slot, or into/out of a section column on a board's published page. Returns both affected slots. A move that would change nothing converges. Requires modify on the board and page-layout API writes enabled for the workspace — otherwise 403 page_layout_api_disabled, which only Playbook can turn on; retrying does not help. Concurrency: pass the version_token from get_page_layout as expected_version_token; if the page changed since, the call answers 409 stale_document and applies NOTHING — read again, re-decide, re-send. A successful write that sent a token returns the NEW version_token: send that on your next write, because your own write already made the old one stale. Of the 409s only lock_wait_timeout and page_layout_library_locked are safe to repeat unchanged. converged: true in the response means nothing changed (the goal state already held); materialized: true means the page had no stored document and this call saved the template's defaults. Both keys are ABSENT when false. The public page can keep showing the old version for up to an hour after a successful write, so a reload may not show the change.

Input Schema

TableJSON Schema

Name	Required	Description
`token`	Yes	Board token of the published board
`at_index`	Yes	0-based destination position.
`column_id`	No	Id to give a column this move CREATES. It does NOT pick an existing column: without column_index the element lands in column 0. Address an existing column with column_index.
`element_id`	Yes	Id of the element to move, from get_page_layout.
`to_slot_id`	Yes	Destination slot (id or name); may equal from_slot_id.
`column_index`	No	Destination section column, by 0-based position.
`from_slot_id`	Yes	Slot currently holding the element (id or name).
`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.
`subboard_token`	No	Edit a nested board's section of this page instead of the page itself: the `collectionToken` of an entry in get_page_layout's `subboards_settings`. Omit for the main page.
`create_new_column`	No	Create a new column in the destination section.
`to_parent_element_id`	No	Move INTO this `section` element's columns.
`expected_version_token`	No	The `version_token` from get_page_layout, echoed verbatim to make this write a compare-and-swap. Omit to write unconditionally.

Schema Changelog

Changes observed during successful MCP inspections.

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",
-  "element_id",
-  "from_slot_id",
-  "to_slot_id",
-  "at_index",
-  "context"
-]New value: +[
+  "token",
+  "element_id",
+  "from_slot_id",
+  "to_slot_id",
+  "at_index"
+]

First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Far exceeds the annotation bar: it names the 403 error code and states that only Playbook can enable it (retrying is futile), explains that a 409 `stale_document` applies NOTHING, describes version-token rotation on success and the resulting staleness of the caller's own token, distinguishes retry-safe from non-retry-safe 409s, and discloses the up-to-one-hour public-page lag. It also clarifies that `converged`/`materialized` keys are ABSENT when false.

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?

Eight dense sentences with the core purpose front-loaded and no filler, but the token/concurrency block is packed tightly and could be split for readability. Given the complexity and the absence of an output schema, nearly every sentence carries weight.

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 12-parameter mutating tool with no output schema, the description supplies the missing pieces an agent needs: auth requirements, all relevant error codes and their remedies, concurrency protocol, and the meaning of the response keys (including when they are absent). Nothing material is left unstated.

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 coverage is 100%, so the schema already documents all 12 parameters including the column_id vs column_index trap and expected_version_token's compare-and-swap role. The description adds behavioral meaning to the version token round-trip but no parameter-level detail the schema lacks, which is the baseline-3 case.

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 opening sentence states a specific verb (move), resource (page element), and the three distinct move targets: position, slot, or into/out of a section column. It also announces the return shape ('Returns both affected slots'), which cleanly separates it from siblings like reorder_page_slot and update_page_element.

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 explicit preconditions ('Requires `modify` on the board and page-layout API writes enabled') and a precise recovery protocol for 409s, including which two are safe to retry. What it lacks is any explicit comparison to adjacent siblings (reorder_page_slot, update_page_element), so the agent must infer when a move is the right call from the move semantics alone.

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?