xTiles

xtiles_get_page_layout

Read-onlyIdempotent

Read the grid layout of an xTiles page (view) by viewId: every tile with its title and grid position (x, y, w, h), plus the grid width, the visible height (pages grow further down) and the minimum tile size. Coordinates use the xTiles grid — (x, y) is the tile’s top-left corner and (w, h) is its size, in grid cells. Use this to inspect tile placement and valid bounds before repositioning with xtiles_set_page_layout. On a text page the tile layout is fixed and the answer says it is not editable. Which colours, styles, sizes and positions to use: xtiles://guide/markdown/design.

Input Schema

Name	Required	Description	Default
`viewId`	Yes	View ID of an xTiles page. You can also extract it from a page URL — it is the last path segment, whatever the domain, e.g. `https://xtiles.app/6740858058af8a09bf6096e6` → viewId is `6740858058af8a09bf6096e6`. Discover IDs programmatically via `xtiles_list_projects` or `xtiles_get_project_content`.

Output Schema

Name	Required	Description	Default
`grid`	Yes
`tiles`	Yes
`view_id`	Yes
`editable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / editable

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: text pages have a fixed layout that the response flags as not editable, and it defines the coordinate system semantics. It stops short of describing pagination or size limits for very tall 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?

The purpose and scope are front-loaded in the first sentence, and the usage instruction follows. It is dense rather than padded, though the coordinate-system explanation and the guide URI reference add length that a terse agent may not need inline.

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?

An output schema exists, so return values need not be re-explained, yet the description still supplies coordinate semantics, the text-page edge case, and a pointer to the design guide for valid style/position values. Nothing an agent needs to call and interpret this read tool 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?

There is a single required parameter with 100% schema description coverage, including how to extract `viewId` from a page URL, so the schema already does the work. The description's coordinate discussion (x, y, w, h) describes the response shape rather than adding meaning to the input parameter, 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?

The description names a specific verb and resource ("Read the grid layout of an xTiles page (view) by `viewId`") and enumerates the payload: every tile with title and grid position, grid width, visible height, and minimum tile size. This is clearly distinguishable from siblings like `xtiles_get_view_content` (content, not layout) and `xtiles_set_page_layout` (write counterpart).

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?

Explicitly states the use case — "inspect tile placement and valid bounds before repositioning with `xtiles_set_page_layout`" — naming the alternative tool and the sequencing condition. It also covers a when-not case: on a text page the layout is fixed and the answer reports it as not editable.

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

All xTiles 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.

Resources

Need Help?