Page Lemon

Make page content a list

bind_list

Destructive

Turns repeated blocks on a page (a menu) into a list: the first call previews items and markup; with confirm_token it creates the list, adds the items and publishes the page.

Input Schema

Name	Required	Description
`list`	Yes
`path`	Yes	Page, e.g. menu.html
`site`	Yes
`fields`	Yes	{field: selector in a block; "": the block}
`import`	No	Add items to a list that has some
`selector`	Yes	Repeated blocks, e.g. ".menu li"
`confirm_token`	No

Output Schema

Name	Required	Description	Default
`blocks`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / blocks
```
Added value: +{
+  "type": "number"
+}
```

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"
```

Changed4 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"

removedInput schema / properties / selector / maxLength
```
Removed value: -200
```

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

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint, non-idempotent and open-world, so safety is partly covered; the description adds the crucial two-step behavior (first call only previews items and markup, repeat with confirm_token to actually create and publish). That is real context beyond the annotations, though it does not say whether the publish step is reversible 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.

Conciseness5/5

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

One compact sentence front-loads the core transformation, then the two-mode behavior, with no filler. Every clause carries information an agent needs.

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

Completeness3/5

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

With an output schema present, return values need no explanation, and the preview/confirm flow plus publish side effect are disclosed. Still, for a destructive 7-parameter mutation, it omits what the preview returns, whether the publish can be undone (undo_list_change exists), and the role of import/list.

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 57%; selector, fields and path are documented in the schema, and the description adds the meaning of confirm_token (triggering creation rather than preview). But list, import and site get no explanation in either place, so it does not fully compensate for the coverage gap.

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?

States a specific verb and outcome: turns repeated blocks (a menu) on a page into a list, and names the exact input shape (repeated blocks). The two-phase preview/confirm behavior further distinguishes it from list-creation siblings like save_list or add_list_items.

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 when it applies (only when content is repeated blocks such as a menu) and explains the confirm_token sequence, which is useful usage context. However, it never explicitly contrasts with add_list_items, import_list_items, or save_list, so an agent must infer which list tool to pick.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?