Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_remove_layout_section

Destructive

Remove a layout section by its section__ slug while keeping its fields in the surrounding record view. Previews by default; set confirm:true to apply.

Instructions

Remove a section from an application's record-view layout by its section__… slug. Requires schema-write. Removes only the section grouping; fields that were under it are preserved (they just rejoin the surrounding layout). Dry-run preview unless confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe section slug (section__…) to remove.
tabIdNoWhich layout to edit when tabs are enabled (REQUIRED then): a tab id, "all" for every tab, or "top" for the hidden top-level layout. Omit only when tabs are disabled.
confirmNoMust be true to apply (default false = preview).
applicationIdYesThe application (table) ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4.2/5.0
Behavior4/5

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

Adds detail beyond annotations: requires schema-write (mutation), dry-run behavior, and non-destruction of fields. Annotations indicate destructive, but description clarifies scope.

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 concise sentences, front-loaded with purpose. No unnecessary words, every sentence adds value.

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?

Covers key aspects: purpose, effect, permission, preview behavior. Lacks error conditions or exact slug format, but sufficient for an AI to use correctly.

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 baseline 3. Description adds minimal extra meaning: slug pattern 'section__…' and confirm default false. Does not add to other parameters.

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?

Clearly states verb 'Remove', resource 'section from layout', and identifier 'section__… slug'. Distinguishes from sibling tools like 'add_layout_section' and 'update_layout_section' by specifying it removes only the grouping, preserving fields.

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 context: requires 'schema-write' permission, explains dry-run preview unless confirm=true, and clarifies that fields are preserved. Does not explicitly state when not to use, but the distinction is clear.

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