Skip to main content
Glama

update_uib_page

Idempotent

Modify an existing UI Builder page by updating its title, route path, or layout using the page sys_id to keep page details accurate.

Instructions

Update an existing UI Builder page (title and/or route path). [Write]

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": {
      "sys_id": "<sys_id>"
    },
    "name": "update_uib_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
titleNo
layoutNo
sys_idYesUIB page sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, and the '[Write]' marker merely restates that. The description adds nothing beyond them: it does not say whether omitted fields are left untouched, what happens to unpublished page state, or that changes are staged in an update set. With annotations carrying the safety profile, this is a thin addition.

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?

One short sentence, front-loaded with the verb and resource, with no filler. The '[Write]' tag is redundant with the annotations, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 25% schema coverage, no output schema, and an undocumented layout parameter, the description leaves real gaps: the scope of updatable fields, the update-set requirement, and any return/confirmation behavior. Annotations cover safety but not the domain preconditions an agent needs.

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 only 25% (sys_id documented), so the description must carry weight; it clarifies that title is the page title and path is the route path, but leaves the layout parameter entirely unexplained. It partially compensates, and the required sys_id is already covered by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Update) and a specific resource (an existing UI Builder page), and scopes it to title and/or route path, which separates it from create_uib_page, delete_uib_page, and update_uib_component. It stops short of 5 because the parenthetical field list is incomplete against the schema (layout is not mentioned).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The word 'existing' implies the page must already exist, but there is no explicit when-to-use versus alternatives such as update_uib_component or create_uib_page, and no prerequisite guidance. Notably it says nothing about needing an active update set, which the sibling set (ensure_active_update_set, complete_update_set) suggests is a real precondition.

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