Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get page

get_page
Read-only

Retrieve a page's full content, layout, custom fields, SEO metadata, and version by ID or slug. Use it to inspect a specific page's structure or SEO settings.

Instructions

Get one page's full details (blocks, layout, page type, custom fields, the SEO title/description/display name per language, and its version - pass it as expectedVersion to patch_block_content) by id or slug. Use when the user asks about a specific page's content, structure or SEO.

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": {
      "idOrSlug": "<idOrSlug>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo'draft' (default) returns the shared page draft. 'devDraft' additionally returns YOUR per-user dev draft overlay in `devDraft` (null when you have none).
idOrSlugYesThe page's id or slug (from list_pages or search_content)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "idOrSlug"
      +]
  2. First observedv0.73.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds genuinely useful context by noting the returned version is meant to be passed as expectedVersion to patch_block_content, which hints at an optimistic-concurrency workflow. Beyond that it does not discuss pagination, draft-vs-published semantics, or what a missing page looks like.

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?

Two sentences, front-loaded with the resource and its full return payload, followed by the usage trigger. The long parenthetical is dense but every item in it is informative; slight tightening would still help readability.

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?

For a two-parameter read tool with full schema coverage and no output schema, the description does the heavy lifting by enumerating the returned fields and linking the version field to patch_block_content. What remains thin is draft-vs-devDraft behavior and error/empty cases, which are partially but not fully covered by the schema.

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%, and the target enum is fully documented in the schema, so the baseline applies. The description reinforces 'by id or slug' and gives the returned version a downstream purpose, but that is output usage rather than input parameter meaning; it adds little the schema doesn't already say.

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?

States a specific verb and resource ('Get one page's full details') and enumerates exactly what comes back: blocks, layout, page type, custom fields, per-language SEO fields, and version. That level of specificity makes it immediately distinguishable from list-oriented siblings and from patch_block_content, which is explicitly named.

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?

'Use when the user asks about a specific page's content, structure or SEO' gives a clear positive trigger, and the description points to list_pages/search_content as the source of the id/slug, implying those are the discovery tools to use first. It stops short of an explicit when-not or 'use the list tools instead if you don't have an id', so it falls just under a 5.

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

Deploy Server

Other Tools