Pixelesq

Get page content

get_page_content

Read-only

Get the actual text content of a page's sections (titles, descriptions, CTAs, images, items). Use this to read what's on the page before editing.

By default the result is a compact outline: per section its id, logicalId, name and type, and per uislice its id, type, collectionId and content (ctx), with empty values left out and each icon's svgStr markup replaced by a short reference such as svg:1a2b3c4d. Send such a reference back unchanged and the icon is kept. Layout settings (cfg) are left out: pass mode "full" for every section's cfg, or read one section with get_section_content. latestRevision.version is the lastVersion a save needs, and latestRevision.headAnchor binds a publish to what was reviewed. The text names the page, revision and section ids too.

Input Schema

Name	Required	Description	Default
`mode`	No	outline (default): content without layout settings; full: every field, including cfg and icon markup	outline
`pageId`	Yes	The page ID
`projectId`	Yes	The project ID

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`slug`	No
`status`	No
`latestRevision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / mode

Added value: +{
+  "default": "outline",
+  "description": "outline (default): content without layout settings; full: every field, including cfg and icon markup",
+  "enum": [
+    "outline",
+    "full"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "latestRevision": {
+      "additionalProperties": {},
+      "properties": {
+        "headAnchor": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "sections": {
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Despite readOnlyHint already marking this as a safe read, the description adds substantial behavioral detail: default outline behavior, omitted cfg fields, icon svgStr replacement with short references, and how references should be sent back unchanged. It also explains latestRevision.version for saves and headAnchor for publish review, which is valuable operational context beyond annotations.

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 description is front-loaded with the purpose and then proceeds through output shape, icon references, layout settings, and revision semantics. It is dense and somewhat long, but the detail is relevant for a tool with non-obvious return behavior and does not read as wasteful.

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?

An output schema exists and annotations already cover the safety profile, yet the description still supplies the key content-shape and save/publish semantics an agent needs to call and interpret this tool correctly. Nothing essential appears to be missing for a read tool of this complexity.

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 projectId, pageId, and mode. The description explains the default outline result and what mode "full" includes, but most of that meaning is already present in the schema's mode description, so it does not add much parameter-specific value beyond the baseline.

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 gives a specific verb and resource: it gets the actual text content of a page's sections, including titles, descriptions, CTAs, images, and items. It also distinguishes the tool from at least one sibling by directing single-section reads to get_section_content.

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?

It explicitly says to use this tool to read what is on the page before editing, and it gives a clear alternative for reading just one section via get_section_content. However, it does not explain when to choose this over other related sibling tools such as get_page or get_partial_content.

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

All Pixelesq tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?