Page Lemon

Read lists

get_lists

Read-onlyIdempotent

Reads Lists: a site's lists (menu, team; shown on its pages) and its form replies and bookings (private). No site: counts for every site. With list: its items, filtered. Marks nothing read.

Input Schema

Name	Required	Description
`q`	No	Text anywhere
`to`	No
`sum`	No	Numbers: {op, field, by}
`from`	No
`list`	No	Its items
`site`	No
`view`	No	Saved filter
`limit`	No
`scope`	No	No site: all, personal, workspace:<id>
`since`	No
`state`	No	Bookings: upcoming\|…\|all
`where`	No	{column: value}
`cursor`	No
`expand`	No	Linked items' fields
`export`	No	A download link
`status`	No	Form replies: new\|read\|spam\|archived\|binned\|all
`service`	No
`resource`	No

Output Schema

Name	Required	Description	Default
`items`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026

addedInput schema / properties / sum

Added value: +{
+  "description": "Numbers: {op, field, by}",
+  "type": "object"
+}

addedInput schema / properties / where / anyOf

Added value: +[
+  {
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / where / type
```
Removed value: -"object"
```

Changed2 schema fields changedOct 27, 2026

removedInput schema / properties / site / description
```
Removed value: -"None: every site, counts only"
```

changedInput schema / properties / status / description

Previous value: -"Messages: new|read|spam|archived|binned|all"New value: +"Form replies: new|read|spam|archived|binned|all"

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

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

Changed3 schema fields changedOct 21, 2026

removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
removedInput schema / properties / where / additionalProperties
```
Removed value: -{}
```

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

B3.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds two real behavioral traits: entity visibility ('shown on its pages' vs 'private') and 'Marks nothing read', which tells the agent this read has no side effects on form-reply status, distinguishing it from mark_form_replies. Pagination and filtering behavior are still undisclosed.

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?

It is short and front-loads the resource, but the sentence-fragment style ('No site: counts for every site.', 'Marks nothing read.') sacrifices parseability for brevity. For an 18-parameter polymorphic tool it is under-specified rather than efficiently concise.

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?

An output schema exists, so return shape needn't be explained, but the tool has 18 optional parameters and multiple modes, and the description omits pagination, filtering (where/view/q), export formats, and how mode interacts with scope. An agent could not reliably compose a valid call from this text alone.

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 56%, so the schema documents roughly half the parameters and the description must carry more weight. It adds meaning for site, list, and scope ('No site: all, personal, workspace:<id>' pattern) and ties status/state to form replies and bookings, but says nothing about q, where, sum, expand, export, limit/cursor, or service/resource, leaving roughly a dozen parameters semantically thin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does state the resource (lists, form replies, bookings) and encodes three distinct modes: no site -> per-site counts, site -> that site's lists, list -> its items. However, the telegraphic phrasing ('Reads Lists: a site's lists (menu, team; shown on its pages)') forces the agent to decode intent, and no sibling is named or excluded (e.g. get_site, export_app_data, save_list).

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?

It provides mode-selection conditions ('No site: counts for every site', 'With list: its items, filtered'), which is genuine routing guidance for a polymorphic tool. But it never states when to prefer this over overlapping siblings, and prerequisites or required parameter combinations per mode are left implicit.

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?