Skip to main content
Glama

Get a page

get_page
Read-onlyIdempotent

Use this when you need one page in detail: its title, whether it is published or a draft, a link to view it, and what it is built from. Find the page handle with list_pages first. Not for changing the page (use update_page or apply_page_edits).

It returns a summary of the page's blocks, and what apply_page_edits needs for precise edits: the draft outline (the theme, and each page's blocks with their id, type, layout and content), its version, and the vocabulary: every block type the page can hold, with its layouts and each field's limits. format is site for a launch page and status for the status page, the page each signup lands on. A status page's outline and vocabulary also hold status, its own settings, and its vocabulary marks the three blocks it cannot be without as required.

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

Input Schema

NameRequiredDescriptionDefault
pageYesThe page handle, like `pg_…`. From `list_pages`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description is free to add substance, which it does: it explains the returned outline/version/vocabulary payload and its role in enabling precise apply_page_edits calls. It does not mention pagination, size limits, or what happens for a nonexistent handle, which keeps it short of a 5.

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 first paragraph is tightly front-loaded with the use case, prerequisite, and exclusions. The second paragraph is information-dense but long, packing return-value semantics and the site/status format distinction into a few sentences without filler.

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 no output schema, the description carries the full burden of explaining returns, and it does so thoroughly: outline, version, vocabulary, the format values, and the extra status-page fields. For a one-parameter read tool, an agent has everything needed to call it and interpret the result.

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?

There is a single parameter and schema description coverage is 100%, with the schema already stating it is a handle 'like `pg_…`' sourced from `list_pages`. The description repeats that provenance ('Find the page handle with `list_pages` first') but adds no new syntax, format, or validation meaning, so the baseline of 3 applies.

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 opens with a specific verb and resource ('need one page in detail') and enumerates what it returns: title, published/draft state, view link, and block composition. It explicitly distinguishes itself from siblings by naming update_page and apply_page_edits as the tools for changing a page.

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

Usage Guidelines5/5

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

It states when to use it ('when you need one page in detail'), a prerequisite ('Find the page handle with list_pages first'), and when not to use it ('Not for changing the page'), pointing to the two concrete alternatives. This is explicit when/when-not/alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.