remnus

get_page

Read-only

Read a page, database row or dashboard by id (type auto-detected; a dashboard comes back as its block spec). mode: "outline" returns headings + first line per section — a cheap skim for a long page (the map shows body sizes) before a full read.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No		full
`pageId`	Yes	Page or row id
`includeComments`	No	Also return the comment thread

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	No	Dashboard only: where a human can see it
`icon`	No
`mode`	No	"outline" when collapsed
`spec`	No	Dashboard only: the block spec (outline mode: `blocks` with id/type/title instead)
`type`	Yes	page \| database \| database_row \| dashboard
`title`	No
`content`	No	Markdown body (collapsed in outline mode); absent for a dashboard
`comments`	No	Present only when includeComments is true
`databaseId`	No
`properties`	No	Database-row properties (rows only)
`recurrence`	No	Present when this row is one occurrence of a repeating series: seriesId, occurrenceDate, detached, rule, occurrences
`fullContentChars`	No	Full body size in chars (outline mode) — gauge whether a "full" fetch is worth it

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 24, 2026

changedInput schema / properties / includeComments / description

Previous value: -"Include the page's comment thread (default false, so ordinary reads stay cheap)"New value: +"Also return the comment thread"

removedInput schema / properties / mode / description

Removed value: -"\"full\" (default) returns the whole markdown body; \"outline\" returns only headings + the first line of each section — use it to skim long pages cheaply, then re-fetch with \"full\" if needed"

changedInput schema / properties / pageId / description

Previous value: -"The workspace item ID or database row ID"New value: +"Page or row id"

changedOutput schema / properties / content / description

Previous value: -"Markdown body (collapsed in outline mode)"New value: +"Markdown body (collapsed in outline mode); absent for a dashboard"

addedOutput schema / properties / spec

Added value: +{
+  "description": "Dashboard only: the block spec (outline mode: `blocks` with id/type/title instead)"
+}

changedOutput schema / properties / type / description

Previous value: -"page | database"New value: +"page | database | database_row | dashboard"

addedOutput schema / properties / url

Added value: +{
+  "description": "Dashboard only: where a human can see it",
+  "type": "string"
+}

Changed3 schema fields changedSep 10, 2026

addedInput schema / properties / includeComments

Added value: +{
+  "default": false,
+  "description": "Include the page's comment thread (default false, so ordinary reads stay cheap)",
+  "type": "boolean"
+}

addedOutput schema / properties / comments

Added value: +{
+  "description": "Present only when includeComments is true",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "authorKind": {
+        "description": "human | agent",
+        "type": "string"
+      },
+      "authorLabel": {
+        "type": "string"
+      },
+      "body": {
+        "type": "string"
+      },
+      "createdAt": {},
+      "id": {
+        "type": "string"
+      },
+      "kind": {
+        "description": "note | closure",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "body",
+      "kind",
+      "authorKind",
+      "authorLabel",
+      "createdAt"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / recurrence

Added value: +{
+  "description": "Present when this row is one occurrence of a repeating series: seriesId, occurrenceDate, detached, rule, occurrences"
+}

Changed9 schema fields changedJul 8, 2026

changedOutput schema / properties / content / description

Previous value: -"Markdown content (collapsed to headings + first lines when mode is \"outline\")"New value: +"Markdown body (collapsed in outline mode)"

removedOutput schema / properties / databaseId / description

Removed value: -"Associated database ID (database items only)"

changedOutput schema / properties / fullContentChars / description

Previous value: -"Size of the full content in characters (outline mode only) — gauge whether a \"full\" fetch is worth it"New value: +"Full body size in chars (outline mode) — gauge whether a \"full\" fetch is worth it"

removedOutput schema / properties / icon / description
```
Removed value: -"Page icon"
```
removedOutput schema / properties / id / description
```
Removed value: -"Page ID"
```

changedOutput schema / properties / mode / description

Previous value: -"Present (\"outline\") when the content was collapsed"New value: +"\"outline\" when collapsed"

changedOutput schema / properties / properties / description

Previous value: -"Database-row properties (database rows only)"New value: +"Database-row properties (rows only)"

removedOutput schema / properties / title / description
```
Removed value: -"Page title"
```

changedOutput schema / properties / type / description

Previous value: -"Resolved type (page | database)"New value: +"page | database"

Changed4 schema fields changedJul 4, 2026

addedInput schema / properties / mode

Added value: +{
+  "default": "full",
+  "description": "\"full\" (default) returns the whole markdown body; \"outline\" returns only headings + the first line of each section — use it to skim long pages cheaply, then re-fetch with \"full\" if needed",
+  "enum": [
+    "full",
+    "outline"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / content / description

Previous value: -"Markdown content"New value: +"Markdown content (collapsed to headings + first lines when mode is \"outline\")"

addedOutput schema / properties / fullContentChars

Added value: +{
+  "description": "Size of the full content in characters (outline mode only) — gauge whether a \"full\" fetch is worth it",
+  "type": "number"
+}

addedOutput schema / properties / mode

Added value: +{
+  "description": "Present (\"outline\") when the content was collapsed",
+  "type": "string"
+}

First observedJun 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. It goes beyond by explaining the type auto-detection, the dashboard spec behavior, and the definition of outline mode. This adds helpful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loads the primary function. The mode explanation is efficiently included, and the guidance on using outline as a skim is optimized for agent decision-making.

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?

Given the output schema exists, the description needn't explain return values. It covers the key nuances (type auto-detection, dashboard behavior, outline mode) that an agent needs to invoke correctly. It doesn't mention pagination or rate limits, but these are minor given the tool's simplicity and read-only nature.

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 covers all three parameters with descriptions for pageId and includeComments, and mode has an enum. The description clarifies the 'outline' option and what it returns, adding some value beyond the schema. However, most parameter semantics are already in the schema, so a 3 is appropriate.

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 clearly states the tool reads various resource types by id, auto-detects type, and returns a dashboard as its block spec. It names specific resources (page, database row, dashboard) and distinguishes from siblings that list or search.

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?

Provides clear guidance on when to use 'outline' mode as a cheap skim before a full read, and mentions the map shows body sizes. It doesn't explicitly exclude alternatives like query_database or get_pages, but the context is clear.

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

All remnus tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

get_page

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources