Skip to main content
Glama

Cleotic

by io.github.generaldataworks
OverviewDiscussionsAdmin

List pages

list_pages
Read-onlyIdempotent

The brand's Content Studio pages by lane: in_progress, live, or needs_refresh, with drafting progress and, once live, AI crawler reads and the answers that name or cite the brand. Start here to find a page_id for get_page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
laneNoOptional filter.
brandYesBrand or study: its ID from list_brands, or its name (exact or a unique prefix).
limitNoRows per page. Defaults to 25, max 100. A page may hold fewer rows to stay within the response size; follow next_cursor.
cursorNonext_cursor from the previous page. Leave out for the first page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
generated_atYesRFC 3339 time the response was made.
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / brand / minLength
      Added value: +1
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from the previous page."New value: +"next_cursor from the previous page. Leave out for the first page."
    • changedInput schema / properties / limit / description
      Previous value: -"Rows per page. Defaults to 25, max 100."New value: +"Rows per page. Defaults to 25, max 100. A page may hold fewer rows to stay within the response size; follow next_cursor."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "brand": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "description": "The brand's website, or empty when none is set.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        "pages": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "claims_to_refresh": {
+                "description": "Claims that may be out of date when the refresh is due.",
+                "type": "integer"
+              },
+              "content_type": {
+                "type": "string"
+              },
+              "crawlers": {
+                "description": "AI crawlers that have read it since it went live.",
+                "type": "integer"
+              },
+              "id": {
+                "description": "Page ID for get_page.",
+                "type": "string"
+              },
+              "lane": {
+                "description": "in_progress, live, or needs_refresh.",
+                "type": "string"
+              },
+              "live_at": {
+                "type": "string"
+              },
+              "new_first_citation": {
+                "description": "An AI answer cited it for the first time since it was last viewed.",
+                "type": "boolean"
+              },
+              "question": {
+                "type": "string"
+              },
+              "refresh_due_at": {
+                "type": "string"
+              },
+              "results": {
+                "additionalProperties": false,
+                "description": "Once live: AI answers to its question that name or cite the brand.",
+                "properties": {
+                  "answers": {
+                    "type": "integer"
+                  },
+                  "cited": {
+                    "description": "Answers that cite the page.",
+                    "type": "integer"
+                  },
+                  "named": {
+                    "description": "Answers that name the brand.",
+                    "type": "integer"
+                  }
+                },
+                "required": [
+                  "answers",
+                  "named",
+                  "cited"
+                ],
+                "type": [
+                  "null",
+                  "object"
+                ]
+              },
+              "sections_drafted": {
+                "type": "integer"
+              },
+              "sections_total": {
+                "type": "integer"
+              },
+              "stage": {
+                "description": "writing, live, read (AI crawlers read it), mentioned, cited, or refresh.",
+                "type": "string"
+              },
+              "status": {
+                "description": "draft, generating, generated, failed, published, or archived.",
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              },
+              "updated_at": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "title",
+              "question",
+              "content_type",
+              "lane",
+              "stage",
+              "status",
+              "sections_drafted",
+              "sections_total",
+              "live_at",
+              "results",
+              "crawlers",
+              "refresh_due_at",
+              "claims_to_refresh",
+              "new_first_citation",
+              "updated_at"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "pagination": {
+          "additionalProperties": false,
+          "properties": {
+            "next_cursor": {
+              "description": "Pass as cursor to get the next page; empty on the last page.",
+              "type": "string"
+            },
+            "total": {
+              "description": "Items across all pages; null when not counted.",
+              "type": [
+                "null",
+                "integer"
+              ]
+            }
+          },
+          "required": [
+            "next_cursor",
+            "total"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "brand",
+        "pages",
+        "pagination"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "description": "RFC 3339 time the response was made.",
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "generated_at",
+    "data"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, read-only listing, so the description's remaining job is to add context, which it does: it discloses what the rows contain (drafting progress, and for live pages AI crawler reads and brand-naming/citing answers) and that lane membership reflects page lifecycle stage. It stops short of describing ordering or how many rows to expect, but that is minor and partly covered by the schema.

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?

A single dense sentence, front-loaded with the verb and resource, followed immediately by the follow-up action. No filler, no restatement of the title, and every clause carries information.

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

Completeness4/5

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

With an output schema present, the description need not explain the return shape, and it correctly focuses on purpose, lane semantics, and the get_page handoff. Pagination (limit/cursor/next_cursor) is left entirely to the schema, which is acceptable but leaves the listing-lifecycle behavior slightly unstated in prose.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by giving semantic meaning to the lane enum values: it explains that 'live' pages surface crawler reads and cited answers, and that needs_refresh signals staleness, which the raw enum strings do not convey.

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 names a specific verb and resource ('list the brand's Content Studio pages') and scopes it by lane. It is immediately distinguishable from get_page, create_page, and draft_page in the sibling list because it is the enumeration tool, and it explicitly frames itself as the entry point ('Start here to find a page_id for get_page').

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 a clear usage context: use this first to obtain a page_id for get_page, and it enumerates the three lane values an agent can filter by. It does not state exclusions (e.g., when to prefer list_brands or search_docs instead), but the routing intent is explicit rather than implied.

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

All Cleotic toolsInspect
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