Skip to main content
Glama

delete_uib_page

Destructive

Delete a UI Builder page and its routes and screen variants by sys_id to remove obsolete screens from ServiceNow.

Instructions

Delete a UI Builder page (screen collection) with its routes and screen variants. [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": "delete_uib_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYesUIB page sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely useful context beyond that: deletion also removes routes and screen variants. It does not say whether deletion is recoverable, whether confirmation is expected, or what the response looks like, so it goes meaningfully beyond annotations but not richly so.

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-loads the effect and cascade scope, with no filler. The '**[Write]**' tag is redundant given readOnlyHint=false but is minor noise rather than a structural problem.

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

Completeness3/5

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

For a single-parameter, destructive delete with no output schema and full annotation coverage, the cascade detail is the essential missing piece and it is present. However, irreversibility, confirmation expectations, and error behavior for an invalid sys_id are left unstated, which matters for a destructive operation.

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 coverage is 100% for the single sys_id parameter, and the description adds no format, source, or lookup guidance for it. Baseline 3 is appropriate when the schema already documents the only parameter.

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?

States a specific verb and resource ('Delete a UI Builder page') and even resolves ambiguity by parenthetically equating it to a screen collection, plus the cascade scope. It doesn't explicitly contrast with sibling tools like get_uib_page or delete_record, but the name/description pair is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of prerequisites, confirmation steps, or alternatives. The reader must infer that this is the destructive variant of the uib_page family from the name alone.

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