Concrete CMS MCP Server

get-pages

Read-only

Retrieve Concrete CMS pages sorted by last updated descending, with pagination and optional content includes.

Instructions

Returns a list of page objects, sorted by last updated descending. The most recent Page objects appear first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-pages"
  }
}

Input Schema

Name	Required	Description
`after`	No	The ID of the current object to start at.
`limit`	No	The number of objects to return. Must be 100 or less. Defaults to 10.
`includes`	No	includes parameter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0-alpha.1Aug 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It contributes the sort order (last updated descending, newest first), which is genuinely useful, but says nothing about pagination behavior, whether results are scoped to a site, or what a page object contains.

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?

Short and front-loaded with the return shape and ordering. The second sentence largely restates the first ('most recent Page objects appear first' vs 'sorted by last updated descending'), which is mild redundancy but not harmful.

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 no output schema, the description should convey enough about the returned collection to use it correctly. It covers ordering but omits pagination semantics (how 'after' advances), whether results span all sites, and any sense of what fields a page object carries.

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 'after', 'limit', and 'includes' including the 100 max and default of 10. The description adds no extra meaning about these parameters, which is acceptable at full coverage but earns only the baseline.

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?

States a specific verb and resource ('Returns a list of page objects') plus an ordering guarantee, which is more than the name alone conveys. It does not distinguish itself from siblings like get-child-pages, get-page-by-id, or get_page_content, so an agent must infer that this is the top-level unfiltered listing.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. Given that get-child-pages and get-page-by-id exist in the same family, the absence of any routing hint leaves the agent to guess which page-listing tool applies.

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