Skip to main content
Glama

xTiles

by app.xtiles
OverviewDiscussionsAdmin

xtiles_update_page

DestructiveIdempotent

Update a page in the project's tab bar — rename it, recolour it and/or archive it: provide title, color, is_archived, or any combination. Get viewId from xtiles_get_project_structure. Only pages listed by xtiles_get_project_structure are valid here. A planner day is not one of them: the API answers 404 for a page in another project and 409 for one inside this project’s planner. Read a planner day with xtiles_get_planner_content and write to it with xtiles_create_tiles_from_markdown_in_project_planner. 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 page. Omit to leave the title unchanged.
viewIdYesView ID of the page to update (from 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
view_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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description carries a lighter burden, but it adds real context: partial updates across any combination of fields, the specific failure modes (404/409), and that the API returns an empty body on success. It does not cover permission/auth requirements, which is the main remaining gap.

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 action and the mutable fields, then the prerequisite, then the planner carve-out. It is dense and slightly digressive in the middle (planner routing), but each sentence supplies information an agent needs to avoid a wrong call.

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 and the description explicitly notes the API returns no body, so return-value expectations are handled. Combined with prerequisites, allowed IDs, error codes and partial-update semantics, nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-parameter descriptions already do the heavy lifting. The description still adds grouping semantics — 'provide title, color, is_archived, or any combination' — clarifying that this is a partial/patch-style update rather than a full replacement, which the schema alone does not state.

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 and resource ('Update a page in the project's tab bar') and enumerates exactly what can be changed (title, colour, archive). It explicitly distinguishes the tool from planner-day writing, which is the main lookalike, so an agent can tell it apart from the create/patch siblings 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 Guidelines5/5

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

Gives the prerequisite source for `viewId` (`xtiles_get_project_structure`) and states the exclusion both positively and negatively: only pages from that structure are valid, a planner day is not, and it names the two sibling tools to use for planner days instead. Error semantics (404 cross-project, 409 planner page) reinforce the boundary.

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