Skip to main content
Glama
Sign In
now-sdk-ext-mcp

now-sdk-ext-mcp

by sonisoft-cnanda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set List Layout

set_list_layout
DestructiveIdempotent

Replaces a table view's full list column layout with a new ordered column list, as saved by the List Layout page; read current layout first and apply to the working update set.

Instructions

Replace a table's list columns for a view with the whole new column list, as the List Layout page saves it, captured and read back. Read it first with get_list_layout. The update set must be the working set.

Input Schema

NameRequiredDescriptionDefault
viewNoThe view; the Default view when omitted.
scopeNoThe record's application: its scope name (e.g. "x_acme_app"), or "global". Give this or scope_id.
tableYesThe table.
columnsYesThe whole new column list, in order.
instanceNoThe ServiceNow instance auth alias to connect to. This is the alias configured via `snc configure` (e.g., "myinstance", "prod", "test"). The user will typically refer to this by name when saying things like "on my myinstance instance". If not provided, falls back to the SN_AUTH_ALIAS environment variable.
scope_idNoThe record's application by sys_scope sys_id, instead of scope.
update_setYessys_id of an In progress update set of that application (create_update_set). The capture is verified there; for adding a column and for layout saves it must also be the working set (set_current_update_set).
acknowledge_upgrade_skipNoOnly for an installed Store application, and only after the user has reviewed the change: upgrades of that application then skip this file until the customization is reviewed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is known. The description adds meaningful context beyond that: the whole column list is replaced (so omitted columns are dropped) and the update set must be the working set for capture verification. It stops short of describing permissions or how the captured change is verified.

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?

Three short sentences, mutation scope front-loaded, followed by the read-first workflow and the update-set constraint. No filler or redundancy.

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?

For an 8-parameter destructive mutation with full schema documentation and no output schema, the description covers the essential workflow dependency and replacement semantics. It could note permission requirements or upgrade-skip context, but nothing critical 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 coverage is 100%, so the schema already documents all eight parameters, including ordering and patterns. The description reinforces that 'columns' is the complete ordered list and that 'update_set' must be the working set, but adds little beyond what the structured fields provide. 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 and resource ('Replace a table's list columns for a view') with explicit scope ('whole new column list'), and contrasts implicitly with set_form_layout by naming the 'List Layout page' as the source of truth. The agent can distinguish it from get_list_layout and the form-layout siblings without opening a schema.

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?

Provides a concrete prerequisite and ordering: 'Read it first with get_list_layout' and 'The update set must be the working set.' It gives clear when-to-use context but does not explicitly exclude alternatives (e.g., when to use set_form_layout instead).

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