Skip to main content
Glama

xTiles

by app.xtiles
OverviewDiscussionsAdmin

xtiles_update_page_group

DestructiveIdempotent

Update a page group in the tab bar — rename it, recolour it and/or archive it: provide title, color, is_archived, or any combination. Archiving a group archives it and its pages together. Get groupId from xtiles_get_project_structure. Never target a group whose system flag is true (the planner) — the API refuses it with a 409, and it should not be attempted. The API answers with no body on success, so there is nothing to return beyond confirmation.

Input Schema

NameRequiredDescriptionDefault
colorNoColour — one of: DEFAULT, LAVENDER, RED, ORANGE, YELLOW, GREEN, DARK_GREEN, LIGHT_BLUE, BLUE, PURPLE, PINK, GRAY, BEIGE. Omit to leave the colour unchanged. `DEFAULT` sets that specific colour; it does not clear/reset the colour — there is currently no way to remove a colour once set. Which colour: first read the project's structure. A page or group listed with `colour <NAME>` has a coloured tab; one listed with only its type (such as `GENERAL`) has no colour. 1) If the tabs are coloured, they are the scheme: a new tab takes the colour of its role in it — an ordinary page the ordinary pages' colour, a group the main page's colour. 2) If no tab has a colour, or the project is new, the colours come from the project's tile colours: the first tile colour gives the ordinary colour, the second the accent; with no coloured tiles, from the topic pair. The ordinary colour goes on every tab; the accent only where the project has a main page — on that page and on every page group. Change one tab at a time, each finishing before the next. Scheme, mapping and when to only offer: `xtiles://guide/markdown/design`, Step 4.
titleNoNew title for the group. Omit to leave the title unchanged.
groupIdYesGroup ID (from xtiles_get_project_structure). Never target a group whose `system` flag is true — see xtiles_get_project_structure.
projectIdYesProject ID (use xtiles_list_projects to discover).
is_archivedNoArchive (true) or unarchive (false) — hides/unhides the item in the tab bar without deleting it. Omit to leave the archived state unchanged. Archived items still appear in xtiles_get_project_structure with is_archived: true, which is how to find one again to unarchive it.

Output Schema

NameRequiredDescriptionDefault
updatedYes
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / color / description
      Previous value: -"Colour — one of: DEFAULT, LAVENDER, RED, ORANGE, YELLOW, GREEN, DARK_GREEN, LIGHT_BLUE, BLUE, PURPLE, PINK, GRAY, BEIGE. Omit to leave the colour unchanged. `DEFAULT` sets that specific colour; it does not clear/reset the colour — there is currently no way to remove a colour once set. Tabs follow a scheme of one or two colours (an ordinary colour on every tab, plus an accent for the main page and groups where there is one, both taken from the project's tile colours); change one tab at a time, each finishing before the next. Scheme and mapping: `xtiles://guide/markdown/design`."New value: +"Colour — one of: DEFAULT, LAVENDER, RED, ORANGE, YELLOW, GREEN, DARK_GREEN, LIGHT_BLUE, BLUE, PURPLE, PINK, GRAY, BEIGE. Omit to leave the colour unchanged. `DEFAULT` sets that specific colour; it does not clear/reset the colour — there is currently no way to remove a colour once set. Which colour: first read the project's structure. A page or group listed with `colour <NAME>` has a coloured tab; one listed with only its type (such as `GENERAL`) has no colour. 1) If the tabs are coloured, they are the scheme: a new tab takes the colour of its role in it — an ordinary page the ordinary pages' colour, a group the main page's colour. 2) If no tab has a colour, or the project is new, the colours come from the project's tile colours: the first tile colour gives the ordinary colour, the second the accent; with no coloured tiles, from the topic pair. The ordinary colour goes on every tab; the accent only where the project has a main page — on that page and on every page group. Change one tab at a time, each finishing before the next. Scheme, mapping and when to only offer: `xtiles://guide/markdown/design`, Step 4."
  2. Changed1 schema field changed
    • changedInput schema / properties / color / description
      Previous value: -"Colour — one of: DEFAULT, LAVENDER, RED, ORANGE, YELLOW, GREEN, DARK_GREEN, LIGHT_BLUE, BLUE, PURPLE, PINK, GRAY, BEIGE. Omit to leave the colour unchanged. `DEFAULT` sets that specific colour; it does not clear/reset the colour — there is currently no way to remove a colour once set."New value: +"Colour — one of: DEFAULT, LAVENDER, RED, ORANGE, YELLOW, GREEN, DARK_GREEN, LIGHT_BLUE, BLUE, PURPLE, PINK, GRAY, BEIGE. Omit to leave the colour unchanged. `DEFAULT` sets that specific colour; it does not clear/reset the colour — there is currently no way to remove a colour once set. Tabs follow a scheme of one or two colours (an ordinary colour on every tab, plus an accent for the main page and groups where there is one, both taken from the project's tile colours); change one tab at a time, each finishing before the next. Scheme and mapping: `xtiles://guide/markdown/design`."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, it discloses that archiving a group also archives its pages, that system groups are rejected with a 409, and that success returns no body. These are meaningful behavioral details for a destructive mutation tool.

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?

The description is front-loaded with the core operation and supported fields, then moves to constraints and API behavior. Every sentence adds useful information without redundancy.

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?

Given the rich annotations, complete schema coverage, and output schema, the description supplies the remaining important context: side effects of archiving, the system-group prohibition, and the no-body success response. Nothing essential 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%, so the schema already documents each parameter in detail, including the color enum and the system-group constraint. The description reinforces how groupId is obtained and what archiving does, but adds little parameter-level information beyond the schema.

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 states a specific verb and resource (update a page group) and enumerates the exact mutable fields: title, color, and is_archived. It is clearly distinguishable from sibling operations such as create_page_group or delete_page_group.

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?

It gives clear guidance on how to obtain groupId from xtiles_get_project_structure and explicitly forbids targeting system groups because the API returns 409. It does not explicitly route the agent to sibling alternatives for creating or deleting groups, but the usage context is otherwise strong.

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

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