Page Lemon

Add list items

add_list_items

Adds items to a list (up to 500); the site shows them within seconds. from copies a form reply: a preview first, then consent and confirm_token after the person's yes.

Input Schema

Name	Required	Description
`copy`	No	{field: form reply field}
`from`	No	Or copy this form reply (itm_…)
`list`	Yes
`site`	Yes
`items`	No	{field: value} each
`consent`	No	The person agreed to be shown
`position`	No	Insert at (1 = first; default: end)
`confirm_token`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / copy / description

Previous value: -"{field: message field}"New value: +"{field: form reply field}"

changedInput schema / properties / from / description

Previous value: -"Or copy this message (itm_…)"New value: +"Or copy this form reply (itm_…)"

Changed1 schema field changedOct 25, 2026
- removedInput schema / properties / list / description
```
Removed value: -"List name"
```
Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / confirm_token
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 22, 2026

removedInput schema / properties / site / description
```
Removed value: -"Site name"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agent_message": {
+      "type": "string"
+    },
+    "change_id": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / items / items / additionalProperties
```
Removed value: -{}
```
removedInput schema / properties / items / maxItems
```
Removed value: -500
```

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

A4.5/5.0

Behavior5/5

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

It adds crucial behavioral context beyond annotations, specifying functional limits (up to 500 items), performance characteristics ('within seconds'), and the complex business logic of using form replies.

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?

The definition is dense but highly efficient, packing functional limits, performance metrics, and a specific usage workflow into two succinct sentences.

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?

Given the high complexity (8 parameters, nested objects), the description provides enough operational logic and workflow constraints for an agent to confidently determine when and how to execute the tool.

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

Parameters4/5

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

With schema coverage at 63%, the description significantly helps define the usage of complex fields, particularly clarifying that parameters like 'copy' and 'from' relate to form replies and their required workflow.

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 clearly states the primary function (adding items to a list). While it doesn't explicitly define the scope relative to all other list manipulation tools, the verb 'Adds' distinguishes it from delete or update operations.

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

Usage Guidelines5/5

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

The description provides a highly specific workflow guideline for usage, detailing the necessary sequence of events involving form replies: preview, consent, and confirmation token required after user agreement.

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?