Skip to main content
Glama

Pages Create

pages_create
Destructive

Create blank pages inside a Google Data Studio report with names, hidden flags, icons, and optional navigation position. Preview changes with dry run and verify outcomes before applying.

Instructions

Create blank pages inside this report, with names, hidden flag and icons.

index is the top-level navigation insertion position; omitted means append. Get structure_fingerprint from report_inspect. Preview IDs are provisional. Multiple API requests may be needed; inspect partial outcomes, never replay blindly. operation_restore reverses a creation when no later edits conflict.

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": {
      "new_pages": "<new_pages>",
      "expected_structure_fingerprint": "<expected_structure_fingerprint>"
    },
    "name": "pages_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo
dry_runNo
new_pagesYes
report_idNo
expected_structure_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.4/5.0
Behavior3/5

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

The destructiveHint=true annotation already flags this as a mutation. The description adds real behavioral context beyond that: preview IDs are provisional, multiple API requests may be needed, partial outcomes must be inspected, and reversal goes through operation_restore. The significant omission is dry_run, which defaults to true in the schema; a destructive tool whose default is a no-op must say so, otherwise an agent may believe a call actually created pages.

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 purpose, then prerequisite, then failure-mode warning; each sentence contributes something. 'Preview IDs are provisional' is terse to the point of ambiguity but is not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. For a destructive, multi-request creation tool the partial-failure and reversal guidance is well targeted, but the unmentioned dry_run default is a material gap in what an agent needs to call this correctly.

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 0%, so the description carries the burden. It successfully explains index (top-level navigation insertion position, omitted means append), the source of expected_structure_fingerprint, and the shape of new_pages entries (name, hidden, icon). It says nothing about dry_run or report_id, leaving two of five parameters without semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create blank pages inside this report') plus the configurable attributes (names, hidden flag, icons). It does not distinguish itself from the sibling pages_import, which presumably also creates pages, so an agent still has to infer which creation path to take.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful prerequisites: fetch structure_fingerprint from report_inspect, and use operation_restore to reverse a creation. It also warns to inspect partial outcomes and never replay blindly. However, there is no explicit when-to-use-this-vs-pages_import guidance and no statement about when creation is inappropriate.

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

Deploy Server

Other Tools