Pixelesq

List pages

list_pages

Read-only

Lists pages in a project. Filter by status (DRAFT|PUBLISHED|IN_REVIEW) or search by name. Returns { results: [{ id, name, slug, status, visibility, updatedAt, hasUnpublishedChanges, meta }], pagination: { offset, limit, total } }; the text names each page's id too. Default limit 20, at most 100. Call before editing or publishing to find the page id.

Input Schema

Name	Required	Description
`limit`	No	Number of pages to return (1 to 100)
`offset`	No	Pagination offset
`search`	No	Search by page name
`status`	No	Only pages with this status. Omit for all pages.
`projectId`	Yes	The project ID

Output Schema

Name	Required	Description	Default
`results`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 22, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of pages to return"New value: +"Number of pages to return (1 to 100)"

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / offset / minimum
```
Added value: +0
```

changedInput schema / properties / offset / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "pagination": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate a safe, closed-world read operation. The description adds useful behavioral context: it names supported filters, default and maximum limits, and describes the returned result and pagination shape.

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 description is front-loaded with purpose, then filters, then return shape and pagination defaults. It is fairly dense but each part is relevant; the return-shape detail is somewhat redundant given the output schema.

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?

With annotations covering safety, 100% schema coverage, and an output schema, the description supplies the remaining practical context: filter options, pagination defaults, return shape, and the workflow reason to call it before editing or publishing.

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 description coverage is 100%, so the schema already documents all five parameters. The description reinforces status filter values and pagination limits, but adds little syntax or meaning beyond the schema.

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 states a specific verb and resource: 'Lists pages in a project.' It distinguishes the tool from get_page by describing list filtering behavior and from create/update siblings by being a read/list operation.

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

Usage Guidelines4/5

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

It gives clear usage context: 'Call before editing or publishing to find the page id.' This helps an agent know when to use it. It does not explicitly exclude alternatives like search_content or get_all_page_statuses, so it falls short of a 5.

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

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

Resources

Need Help?