Concrete CMS MCP Server

get-page-version-by-page-id-and-version-id

Read-only

Retrieves a specific page version using its page ID and version ID, so you can inspect version details or compare content revisions in Concrete CMS.

Instructions

Find a page version by its ID and the ID of its page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageID": "<pageID>",
      "versionID": "<versionID>"
    },
    "name": "get-page-version-by-page-id-and-version-id"
  }
}

Input Schema

Name	Required	Description	Default
`pageID`	Yes	pageID parameter
`versionID`	Yes	versionID parameter

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.7/5.0

Behavior2/5

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

readOnlyHint=true already tells the agent this is a non-mutating read, so the description carries little remaining burden. Still, it adds nothing beyond the annotation — no note on what happens when the version ID doesn't belong to the page, and no indication of the response 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?

A single short sentence with no wasted words, front-loaded with the verb and resource. It is efficient, though it is also nearly a verbatim echo of the name.

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?

For a simple two-path-parameter read tool with no output schema and a readOnlyHint annotation, the minimum is met. It stops short of describing the returned version resource or error behavior for mismatched IDs.

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 baseline is 3, but the schema's own parameter descriptions are placeholders ('pageID parameter', 'versionID parameter'). The description adds only that the version ID belongs to a specific page, which is a marginal clarification of the key relationship.

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 states a specific verb ('Find') and resource ('page version') and clarifies that lookup is keyed on both a page ID and a version ID. However, it largely restates the tool name and does nothing to distinguish it from the sibling get-page-versions-by-page-id, so the purpose is only adequately conveyed.

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 guidance on when to use this tool versus alternatives such as get-page-versions-by-page-id or get-page-by-id. The agent must infer from the name alone that this is the single-version lookup rather than the list operation.

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