Page Lemon

Delete a list

delete_list

Destructive

Deletes a list and its items (a list with items: two steps).

Input Schema

Name	Required	Description	Default
`list`	Yes
`site`	Yes
`confirm_token`	No

Output Schema

Name	Required	Description	Default
`items`	No
`pages`	No
`change_id`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / change_id
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / items
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / pages
```
Added value: +{
+  "type": "array"
+}
```

Changed2 schema fields changedOct 25, 2026

removedInput schema / properties / list / description
```
Removed value: -"List name"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026
- removedInput schema / properties / confirm_token / description
```
Removed value: -"From the first call"
```
Changed2 schema fields changedOct 22, 2026
- changedInput schema / properties / confirm_token / description
```
Previous value: -"From the first call: approval status"New value: +"From the first call"
```
- removedInput schema / properties / site / description
```
Removed value: -"Site name"
```

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / confirm_token / description

Previous value: -"From the first call: re-call with it for the approval status"New value: +"From the first call: approval status"

changedInput schema / properties / site / description

Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

AddedOct 20, 2026

TDQS

C2.7/5.0

Behavior3/5

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

The annotations already mark this as destructive and non-idempotent. The description adds useful context that deleting a list also deletes its items, implying a cascade, but it does not explain the confirm_token, irreversibility, or required permissions.

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?

It is a single front-loaded sentence with no wasted text. The parenthetical is awkward, but the core destructive action is stated immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with an undocumented confirm_token and zero parameter descriptions, the description is too sparse. The output schema means return values need not be explained, but safety and parameter requirements are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain any of the three parameters. It does not clarify what 'site' or 'list' should contain, and it completely omits the presence and purpose of 'confirm_token'.

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 description states a clear verb and resource: it deletes a list and its items. That distinguishes it from save_list and remove_list_items, though it does not explicitly name those alternatives.

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

Usage Guidelines2/5

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

It gives no guidance on when to use this tool versus remove_list_items, undo_list_change, or save_list. The parenthetical '(a list with items: two steps)' is cryptic and does not clarify the usage context.

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

All Page Lemon tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?