Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_move_layout_field

Move a field to a new position in the record-view layout: reorder within the same tab, place under a section, or transfer to another tab. Preview changes unless confirmed.

Instructions

Move/arrange a field in the record-view layout — reorder it, place it under a section, or move it to a different tab. Requires readwrite/admin + SMARTSUITE_ENABLE_SCHEMA_WRITE. To move a field to ANOTHER tab, pass toTab = the destination tab id: the field is removed from its current tab and added to the destination (this is the cross-tab move — plain reorder can't pull a field in from another tab). Otherwise it reorders within the current layout. Pass afterField = a field slug OR a section__ slug to position this field right after it (right after a section marker = first field under that section); omit afterField for the end. In two-column layouts the field is placed as its own full-width row. When tabs are enabled and toTab is NOT used, tabId is required (a tab id, "all", or "top"). Dry-run preview unless confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe field slug to move.
tabIdNoFor within-layout reorder when tabs are enabled (required then): a tab id, "all", or "top". Ignored when toTab is set. Omit when tabs are disabled.
toTabNoDestination tab id — moves the field to that tab (removing it from its current tab). Use this for cross-tab moves.
confirmNoMust be true to apply (default false = preview).
afterFieldNoField slug or section__ slug to place this field after (default: end).
applicationIdYesThe application (table) ID.
Behavior5/5

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

Discloses key behavioral traits: write operation (contradicts readOnlyHint: false but that's consistent), dry-run default unless confirm:true, cross-tab removal behavior, and positioning logic. No contradictions with annotations.

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?

Compact, well-structured description with no redundancies. Each sentence adds value: purpose, usage, parameter details, and edge cases are covered efficiently.

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?

Given 6 parameters, no output schema, and no enums, the description covers all essential aspects: permissions, operation modes, parameter dependencies, and preview/confirm behavior. Leaves no major gaps.

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

Parameters5/5

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

Adds significant meaning beyond the schema: explains afterField semantics (field slug or section__ slug), toTab for cross-tab moves, tabId conditional requirement, and confirm flag role. Enhances understanding despite high schema coverage.

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?

The description uses a specific verb ('Move/arrange') and resource ('field in the record-view layout'), and clearly distinguishes it from sibling layout tools by focusing on field positioning rather than section/tab management.

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 clear context for when to use the tool, including permissions required and parameter guidance for cross-tab vs within-layout moves. Does not explicitly contrast with alternative tools, but the intent is well understood.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartSuiteFoundry/smartsuite-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server