Skip to main content
Glama

move_view_to_section

Idempotent

Move a view to a specific section or position in the Airtable sidebar. Reorder sections and views by specifying target index and optional section ID.

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

Implementation Reference

  • The handler function for the move_view_to_section tool. Destructures appId, tableId, viewIdOrSectionId, targetIndex, and targetSectionId from args, calls client.moveViewOrViewSection, and returns success response.
    async move_view_to_section({ appId, tableId, viewIdOrSectionId, targetIndex, targetSectionId, debug }) {
      const result = await client.moveViewOrViewSection(
        appId, tableId, viewIdOrSectionId, targetIndex,
        targetSectionId === null || targetSectionId === undefined ? undefined : targetSectionId,
      );
      return ok({ updated: true, viewIdOrSectionId, targetIndex, targetSectionId: targetSectionId ?? null }, result, debug);
    },
  • Input schema definition for the move_view_to_section tool, requiring appId, tableId, viewIdOrSectionId, targetIndex with optional targetSectionId and debug.
      {
        name: 'move_view_to_section',
        description: `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.`,
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
        inputSchema: {
          type: 'object',
          properties: {
            appId: { type: 'string', description: 'The Airtable base/application ID' },
            tableId: { type: 'string', description: 'The table ID (tbl-prefixed)' },
            viewIdOrSectionId: { type: 'string', description: 'A view ID (viw...) or section ID (vsc...) to move' },
            targetIndex: { type: 'number', description: 'Destination index (0 = top). Per-section for in-section moves; per-table for section reorders.' },
            targetSectionId: { type: 'string', description: 'Optional vsc-prefixed section ID to move INTO. Omit (or pass null) to move the view to ungrouped.' },
            debug: debugProp,
          },
          required: ['appId', 'tableId', 'viewIdOrSectionId', 'targetIndex'],
        },
      },
  • Input schema definition for the move_view_to_section MCP tool.
      {
        name: 'move_view_to_section',
        description: `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.`,
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
        inputSchema: {
          type: 'object',
          properties: {
            appId: { type: 'string', description: 'The Airtable base/application ID' },
            tableId: { type: 'string', description: 'The table ID (tbl-prefixed)' },
            viewIdOrSectionId: { type: 'string', description: 'A view ID (viw...) or section ID (vsc...) to move' },
            targetIndex: { type: 'number', description: 'Destination index (0 = top). Per-section for in-section moves; per-table for section reorders.' },
            targetSectionId: { type: 'string', description: 'Optional vsc-prefixed section ID to move INTO. Omit (or pass null) to move the view to ungrouped.' },
            debug: debugProp,
          },
          required: ['appId', 'tableId', 'viewIdOrSectionId', 'targetIndex'],
        },
      },
  • The client method moveViewOrViewSection that sends the actual API request to Airtable's /v0.3/table/{tableId}/moveViewOrViewSection endpoint.
    async moveViewOrViewSection(appId, tableId, viewIdOrViewSectionId, targetIndex, targetViewSectionId = undefined) {
      assertAirtableId(appId, 'appId');
      assertAirtableId(tableId, 'tableId');
      if (!viewIdOrViewSectionId) {
        throw new Error('moveViewOrViewSection requires viewIdOrViewSectionId');
      }
      const url = `https://airtable.com/v0.3/table/${tableId}/moveViewOrViewSection`;
      const payload = { viewIdOrViewSectionId, targetIndex: Number.isFinite(targetIndex) ? targetIndex : 0 };
      if (targetViewSectionId) payload.targetViewSectionId = targetViewSectionId;
    
      const res = await this.auth.postForm(url, this._mutationParams(payload, appId), appId);
      if (!res.ok) {
        const errBody = await res.text().catch(() => '');
        throw new Error(`moveViewOrViewSection failed (${res.status}): ${errBody}`);
      }
      this.cache.invalidate(appId);
      return res.json();
    }
  • Registration/Categorization of move_view_to_section in the 'view-section' category in TOOL_CATEGORIES.
    move_view_to_section:   'view-section',
Behavior4/5

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

Annotations already indicate idempotence and non-destructiveness. The description adds behavioral context by detailing the four parameter-dependent actions and the effect of the debug flag. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear introductory sentence and a bullet-like list of scenarios. While a bit lengthy, it efficiently conveys complex behavior without redundancies.

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?

Given no output schema, the description adequately covers all main use cases and parameter interactions. It could mention prerequisites (like valid appId/tableId) or error conditions, but the required parameters and their descriptions provide sufficient context.

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?

With 100% schema coverage, the description still adds value by explaining how viewIdOrSectionId and targetSectionId combine for different moves, and clarifying the meaning of targetIndex per scenario. This goes beyond the schema's basic descriptions.

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 clearly states the tool moves a view or section within the sidebar, and then enumerates four distinct user actions via specific parameter combinations. This explicitly differentiates it from sibling tools like reorder_view_fields or move_visible_columns.

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?

The description explains when to use each variant (view into section, view out to ungrouped, reorder section, reorder within section), providing clear context. However, it does not explicitly mention when not to use this tool relative to alternatives.

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