Skip to main content
Glama

Page Insert Space

page_insert_space
Destructive

Inserts vertical space on a static Datastudio page by moving components at or below a pixel down by a set height and growing the canvas; negative height removes space when no overlap occurs.

Instructions

Make room for a new section: every component starting at or below at_top (pixels) moves down by height, groups as a whole, and the page canvas grows by height. A negative height removes empty space (refused if anything would overlap). One page write with preview, read-back and operation_restore. Static canvas only; page_get fingerprint.

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": {
      "page_id": "<page_id>",
      "at_top": "<at_top>",
      "height": "<height>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "page_insert_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
at_topYes
heightYes
dry_runNo
page_idYes
report_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.1/5.0
Behavior4/5

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

Well beyond the annotations: it discloses that this is a single page write with preview, read-back and operation_restore availability, that groups translate as a whole, that the canvas dimension changes, and that overlap causes refusal. The one gap is that dry_run's default-true preview behavior is only alluded to rather than stated.

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?

Dense and front-loaded: the core movement rule comes first, edge cases (negative height, overlap refusal, static-only) follow. The trailing fragments 'Static canvas only; page_get fingerprint.' are terse but still earn their place as constraints.

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?

A destructive geometry mutation with an output schema and six parameters; the description covers the spatial model, the mutation contract, and the restore path, which is what an agent most needs. Missing are explicit notes on dry_run's default and the fingerprint/report_id roles.

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 must carry parameter meaning. It explains at_top (pixels, the threshold) and height (including negative semantics), but dry_run, report_id, and expected_fingerprint are only hinted at ('preview', 'page_get fingerprint') without stating their roles or defaults.

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 pairs a specific verb (insert space) with a precise mechanism: everything at or below at_top shifts down by height, groups move as a unit, and the canvas grows. 'Static canvas only' scopes the tool against other page types, so an agent can tell what it does and what it does not cover without opening the schema.

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?

'Make room for a new section' names the intent that selects this tool, and the negative-height clause explains the inverse use case (removing empty space) along with its refusal condition. It also points to page_get for the fingerprint. No explicit competing sibling is named, which keeps it just short of a 5.

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