Skip to main content
Glama

show_or_hide_view_columns

Idempotent

Show or hide multiple columns in an Airtable view by passing field IDs and a visibility flag. All specified columns are set to the same visibility in one call.

Instructions

Show or hide specific fields (columns) in a view. Pass an array of column IDs and a single visibility flag — every ID in the array is set to that visibility. To toggle many fields at once, send the full set in one call (no separate "show all" / "hide all" tool exists today; that lives in 2.4.0+).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
viewIdYesThe view ID (e.g. "viwXXX")
columnIdsYesArray of field IDs to show or hide
visibilityYestrue to show, false to hide
debugNoWhen true, include raw Airtable response in output for diagnostics

Implementation Reference

  • Tool handler function for 'show_or_hide_view_columns'. Calls client.showOrHideColumns() with the appId, viewId, columnIds array, and visibility flag, then returns the result.
    async show_or_hide_view_columns({ appId, viewId, columnIds, visibility, debug }) {
      const result = await client.showOrHideColumns(appId, viewId, columnIds, visibility);
      return ok(
        { updated: true, viewId, columnIds, visibility },
        result,
        debug,
      );
    },
  • Client-side implementation of showOrHideColumns. Sends POST to /v0.3/view/{viewId}/showOrHideColumns with payload { columnIds, visibility }. This is the actual Airtable API call.
    /**
     * Show or hide specific columns in a view.
     * Payload: { columnIds: ["fldXXX", ...], visibility: boolean }
     */
    async showOrHideColumns(appId, viewId, columnIds, visibility) {
      assertAirtableId(appId, 'appId');
      assertAirtableId(viewId, 'viewId');
      const url = `https://airtable.com/v0.3/view/${viewId}/showOrHideColumns`;
      const payload = { columnIds, visibility };
    
      const res = await this.auth.postForm(url, this._mutationParams(payload, appId), appId);
    
      if (!res.ok) {
        const errBody = await res.text().catch(() => '');
        throw new Error(`showOrHideColumns failed (${res.status}): ${errBody}`);
      }
    
      return res.json();
    }
  • Schema/definition for the 'show_or_hide_view_columns' tool. Defines input parameters: appId (required), viewId (required), columnIds (array of field IDs, required), visibility (boolean true/false, required), and optional debug.
    {
      name: 'show_or_hide_view_columns',
      description: 'Show or hide specific fields (columns) in a view. Pass an array of column IDs and a single visibility flag — every ID in the array is set to that visibility. To toggle many fields at once, send the full set in one call (no separate "show all" / "hide all" tool exists today; that lives in 2.4.0+).',
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          appId: { type: 'string', description: 'The Airtable base/application ID' },
          viewId: { type: 'string', description: 'The view ID (e.g. "viwXXX")' },
          columnIds: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of field IDs to show or hide',
          },
          visibility: { type: 'boolean', description: 'true to show, false to hide' },
          debug: debugProp,
        },
        required: ['appId', 'viewId', 'columnIds', 'visibility'],
      },
    },
  • Tool config registration mapping 'show_or_hide_view_columns' to the 'view-write' category for profile-based enable/disable.
    show_or_hide_view_columns: 'view-write',
  • Extension-side tool category registration, mirrors the server-side mapping for profile management.
    show_or_hide_view_columns: 'view-write',
Behavior3/5

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

Annotations already declare idempotentHint=true, so agent knows operation is idempotent. Description adds that all column IDs are set to the same visibility, but no additional side effects or authentication needs are mentioned. Adequate but not exceptional.

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?

Two sentences, front-loaded with the primary purpose, no redundant information. Every word serves a purpose.

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 the core operation, batching advice, and a version note. Lacks details on return format or error cases, but for an idempotent mutation with no output schema, this is acceptable. Minor ambiguity about the 2.4.0+ version reference.

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?

Input schema has 100% description coverage for all 5 parameters. Description only reiterates the schema's information (array of column IDs and a single flag) without adding extra meaning or constraints beyond what is already documented.

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 clearly states the action (show or hide) and the resource (specific fields in a view). It distinguishes the tool's behavior from a hypothetical 'show all' tool, though inaccurately noting its existence.

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 guidance: pass an array of column IDs with a single visibility flag, and recommends batching. However, it incorrectly claims no separate 'show all' tool exists (sibling 'show_or_hide_all_columns' is available), potentially confusing an agent.

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