Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

List report pages

list_pages
Read-only

List the pages of a report or dashboard, ordered by position. For a template, use list_template_pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYesReport or dashboard ID (from list_reports)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoOne row per page, in display order — page_id, name, position and visible. Pass page_id to list_widgets to read what is on it.
metaNoPage, limit and total row count.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / report_id
      Added value: +{
+  "description": "Report or dashboard ID (from list_reports)",
+  "type": "string"
+}
    • removedInput schema / properties / source_id
      Removed value: -{
-  "description": "Report or template ID (from list_reports or list_templates)",
-  "type": "string"
-}
    • removedInput schema / properties / source_type
      Removed value: -{
-  "description": "Source type (defaults to \"project\")",
-  "enum": [
-    "project",
-    "template"
-  ],
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "source_id"
-]New value: +[
+  "report_id"
+]
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / meta / description
      Previous value: -"Pagination for the list — page, limit and the total row count."New value: +"Page, limit and total row count."
    • changedOutput schema / properties / meta / properties / limit / description
      Previous value: -"Maximum rows per page."New value: +"Max rows per page."
    • changedOutput schema / properties / meta / properties / page / description
      Previous value: -"Zero-based index of the page returned."New value: +"Page index, zero-based."
    • changedOutput schema / properties / meta / properties / total / description
      Previous value: -"Total rows matching the query across all pages."New value: +"Total rows matching the query."
    • changedOutput schema / properties / success / description
      Previous value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context: pages are ordered by position and the tool applies to both reports and dashboards. It does not contradict annotations.

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?

Two sentences with no filler. The core behavior is front-loaded, and the routing to the template sibling is a single efficient second sentence.

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?

For a single-parameter, read-only, output-schema-backed list operation, the description fully covers purpose, scope, ordering, and the key alternative. Nothing needed for correct invocation is missing.

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%, with report_id already described as 'Report or dashboard ID (from list_reports)'. The description reinforces the report/dashboard scope but does not add meaning beyond the schema, so baseline 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?

Description states a specific verb and resource: list the pages of a report or dashboard, ordered by position. It differentiates from list_template_pages explicitly, so an agent can distinguish it from the closest sibling without inspecting schema.

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?

The description names the exact alternative for templates ('use list_template_pages'), providing clear when-not-to-use guidance. It also clarifies that the tool covers both reports and dashboards, leaving little to inference.

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

All oviond toolsInspect
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