Playbook

Delete page element

delete_page_element

DestructiveIdempotent

Remove an element from a board's published page and return the slot as it now stands. An id that is nowhere on the page succeeds with converged: true, which means nothing was removed. An id that exists but in a different slot than slot_id is a 404. Deleting a section removes its contents with it. 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.

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>",
      "element_id": "<element_id>",
      "slot_id": "<slot_id>"
    },
    "name": "delete_page_element"
  }
}

Input Schema

Name	Required	Description
`token`	Yes	Board token of the published board
`slot_id`	Yes	The slot holding the element (id or name).
`element_id`	Yes	Id of the element to remove, from get_page_layout.
`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.
`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.

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

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 it discloses the no-op success case (`converged: true`), the 404 on a slot mismatch, cascade deletion for `section`, the 403 `page_layout_api_disabled` with the note that retrying is useless, compare-and-swap semantics that apply nothing on 409, which 409s are safe to repeat, version-token rotation after a write, and up to an hour of stale public rendering. That is a rich behavioral layer the annotations do not carry. The single gap: it never addresses `subboard_token`, so an agent editing a nested section gets no warning about scoping behavior.

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

Conciseness3/5

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

The purpose is front-loaded and most sentences carry non-obvious information, but the back half is a dense run-on of error codes, token rotation and cache-lag notes with no structure to separate them. Distinct concerns (auth, concurrency, response keys, eventual consistency) are concatenated rather than grouped, which makes it harder to scan than its length alone would require.

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 description carries the return contract itself, explaining `converged`, `materialized` and the new `version_token` including that absent keys mean false. Auth requirements, concurrency protocol and read-after-write lag are all covered for a destructive write. Only the `subboard_token` path is left 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 coverage is 100%, so the baseline is 3, and the description does earn slightly more by explaining that `element_id` must match `slot_id` or the call 404s, and by framing `expected_version_token` as an opt-in compare-and-swap with 'omit to write unconditionally' semantics. It leaves `subboard_token` and `organization` entirely to 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?

The opening sentence gives a specific verb and resource ('Remove an element from a board's published page') plus the return shape, and the verb 'remove' separates it cleanly from add_page_element, move_page_element and update_page_element. It stops short of naming those siblings explicitly, so the differentiation is inferred from the verb 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 Guidelines4/5

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

It tells the agent to pull `version_token` from get_page_layout and echo it as `expected_version_token`, and it prescribes the recovery loop on 409 ('read again, re-decide, re-send'). What is missing is any explicit routing statement such as when to prefer move_page_element or update_page_element over delete, so there are no stated exclusions.

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?