Skip to main content
Glama

Get one page's details

get_page

Fetch the details of a single published page: its title, private link, total view count, when it was created, when it expires (or 'never'), whether it's searchable, whether it's password-protected, and which project it's filed under. Use this to answer questions like 'how many views does my page have?' or to check a page's current settings before changing them. Identify the page with page (its viewer URL or slug). You can only read your own pages.

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's viewer URL or its slug (the part after the last '/').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the returned fields, that the page must be published, and the access restriction 'You can only read your own pages.' It omits failure behavior (not-found, wrong-owner errors) and whether archived/deleted pages are visible, which keeps it from 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?

Front-loaded with the verb and resource, then the field list, then usage, then the identifier. The field enumeration is long but each item tells the agent what is available without an output schema, so it earns its space; a slightly tighter phrasing would be possible.

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 no output schema and no annotations, the description correctly compensates by naming the returned fields and the access scope. For a single-parameter read tool this is nearly complete; only error/edge-case behavior is unaddressed.

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 coverage is 100% and there is only one parameter, so the schema already documents it fully. The description repeats the same guidance ('viewer URL or slug') without adding format examples or edge-case handling, so it neither adds nor loses meaning.

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 ('Fetch the details of a single published page') and then enumerates the exact fields returned, so an agent knows precisely what it gets. The word 'single' implicitly contrasts with the list_pages sibling, and the scope is unambiguous.

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?

Gives two concrete usage scenarios ('how many views does my page have?' and 'check a page's current settings before changing them'), the latter effectively pointing at update_page. It does not name siblings explicitly or state exclusions, so it stops short of a full when/when-not treatment.

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.

Resources