remnus

get_page

Read-only

Get content of a workspace page or database row by its ID. Auto-detects the type — no flags needed. Pass mode: "outline" for a token-cheap skim (headings + first line of each section) before deciding whether to fetch the full content.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	"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	full
`pageId`	Yes	The workspace item ID or database row ID
`includeComments`	No	Include the page's comment thread (default false, so ordinary reads stay cheap)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`icon`	No
`mode`	No	"outline" when collapsed
`type`	Yes	page \| database
`title`	No
`content`	No	Markdown body (collapsed in outline mode)
`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.

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.5/5.0

Behavior4/5

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

Beyond readonly annotation, it discloses auto-detection of page vs row, and the token-cheap skim behavior of outline mode. It does not document edge cases or failure behavior, but covers the key runtime behavior.

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?

Efficient, front-loaded purpose, then behavioral guidance. Every sentence adds information.

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?

Given a complete output schema and 100% parameter coverage, the description fills the remaining gap by explaining auto-detection and when to use outline mode. No missing context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all parameters with descriptions throughout, so the main description adds little parameter meaning. The outline-vs-full guidance is repeated from schema, but the schema itself is descriptive enough. Slight redundancy to schema, hence not 5.

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 states a specific verb and resource: 'Get content of a workspace page or database row by its ID'. It also notes auto-detection, which differentiates it from siblings like get_pages (plural) and search_workspace.

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 the 'outline' mode ('before deciding whether to fetch the full content') vs full mode dependencies. Does not compare against sibling tools like get_pages or search_workspace, but the purpose is self-contained enough for an agent to select it.

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

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.