remnus

delete_page

Destructive

Delete a workspace page, database, or database row. Requires confirm: true to execute — omit or set false to preview what would be deleted.

Input Schema

TableJSON Schema

Name	Required	Description
`pageId`	Yes	The workspace item ID or database row ID to delete
`confirm`	No	Set to true to confirm deletion. Without this flag, returns a preview of what would be deleted.
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	ID of the deleted item
`deleted`	Yes	Whether the item was actually deleted (false for a preview)
`preview`	No	Preview message when confirm was not set

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / contextRunId

Added value: +{
+  "description": "prepare_context contextRunId. Required for mutations when the workspace uses Strict context.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

First observedJun 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds a crucial behavioral layer: the confirm flag converts the operation into a preview without it. This goes beyond the annotations and explains the two-step deletion flow. It does not cover reversibility or permissions, but the preview mechanism is a significant addition.

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?

The description is a single, well-structured sentence that front-loads the action and immediately explains the confirm requirement. It is concise with zero fluff, and the preview behavior is stated early, making it easy for an agent to grasp the core semantics quickly.

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?

The description covers the essential behavioral requirement (confirm flag) and the tool's scope, and an output schema exists to detail return values. It does not mention the contextRunId requirement for strict contexts or contrast with bulk_delete_pages, but given the schema covers those and the output schema exists, the description is adequately complete for safe usage.

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?

The input schema already provides 100% coverage with clear descriptions for pageId, confirm, and contextRunId. The description reiterates the confirm behavior but does not add new parameter-level insights beyond what the schema states. The mention of database row ID is already in the schema, so the description adds minimal extra value.

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 clearly states the verb 'Delete' and the resource types: workspace page, database, or database row. It also highlights the critical confirm/preview behavior, making it distinct from sibling tools like bulk_delete_pages and delete_database_view. The specificity leaves no ambiguity about what the tool operates on.

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 implies usage for single deletions and mentions the preview mechanism, but it does not explicitly contrast with sibling tools like bulk_delete_pages for multiple items or delete_database_view for views. No when-not-to-use guidance is provided, leaving some routing to the agent to infer from the sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All remnus 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.