xTiles

xtiles_get_tile_styles

Read-onlyIdempotent

Read the color styling of every tile on an xTiles page (view) by viewId: each tile with its title, color (palette background color) and color_size (color variant / border style). Both are null when the tile has no palette color. Use this to inspect current colors before recoloring with xtiles_set_tile_styles. On a text page the tile style is fixed and the answer says it is not editable. It is also where the palette of an existing page is read before adding tiles to it, so the new tiles continue those colours — see 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
`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.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavioral context: color/color_size are null when there is no palette color, and on a text page the style is fixed and the response reports it as not editable. This disclosed edge-case behavior is genuinely useful beyond the annotations.

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-loads the core purpose and the primary usage guidance. The final clause about reading a palette before adding tiles and the external guide reference are mildly tangential and lengthen the description, but nothing is wasteful enough to be a real defect.

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?

With an output schema present the return shape needn't be spelled out, yet the description usefully characterizes the key fields (title, color, color_size) and their null semantics. An agent has everything needed to call it correctly; the guide link is a minor extra.

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?

Only one parameter and schema coverage is 100%, so the schema already documents viewId (including URL extraction). The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (read) and resource (color styling of every tile on a page), scoped by viewId. It clearly distinguishes itself from the sibling mutators xtiles_set_tile_styles and xtiles_reset_tile_styles.

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 says to use it to inspect current colors before recoloring with `xtiles_set_tile_styles`, and describes a second use case (reading an existing page's palette before adding tiles). It names the alternative tool and the conditions that select this one.

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?