Skip to main content
Glama

move_view_to_section

Idempotent

Relocate views into sections or reorder sections and views within an Airtable table's sidebar.

Instructions

Move a view (or a section itself) within the sidebar. The single endpoint covers four user actions depending on the arguments:

  • viewId + sectionId → put the view INTO that section at targetIndex

  • viewId + sectionId: null → move the view OUT to ungrouped at table-level targetIndex

  • sectionId-as-viewIdOrSectionId + targetIndex → reorder the section among other sections

  • viewId + same section → reorder the view within its current section For section reorders, targetIndex is into the table's top-level mixed viewOrder; for in-section moves, it's into that section's viewOrder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
tableIdYesThe table ID (tbl-prefixed)
viewIdOrSectionIdYesA view ID (viw...) or section ID (vsc...) to move
targetIndexYesDestination index (0 = top). Per-section for in-section moves; per-table for section reorders.
targetSectionIdNoOptional vsc-prefixed section ID to move INTO. Omit (or pass null) to move the view to ungrouped.
debugNoWhen true, include raw Airtable response in output for diagnostics
Behavior5/5

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

Annotations already declare idempotentHint=true, not destructive. Description adds substantial behavioral context: explains how targetIndex works differently for section reorders vs in-section moves, and mentions the debug parameter. No contradiction 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?

Description is a single well-structured paragraph with a clear front-loaded purpose statement and numbered list of four cases. Every sentence adds essential behavior info; no fluff.

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 all four use cases and explains targetIndex semantics. However, no mention of return value (no output schema) or error conditions. Given complexity (6 params, 4 required), slightly more context on output/errors would be ideal.

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

Parameters4/5

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

All 6 parameters have schema descriptions (100% coverage). The tool description adds value by explaining the combinatorial semantics (e.g., viewId+sectionId vs viewId+null) and the dual meaning of targetIndex, which goes beyond what each parameter description provides individually.

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?

Description explicitly states it moves a view or section within the sidebar and enumerates four distinct use cases with argument patterns. This clearly differentiates it from sibling tools like create_view or reorder_view_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?

Description lists four specific actions and their argument combinations, implicitly guiding when to use each variant. However, it does not explicitly state contraindications or compare with alternative tools.

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/Automations-Project/VSCode-Airtable-Formula'

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