Skip to main content
Glama
Praroop1435

Airtable Full-Stack MCP

by Praroop1435
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

airtable_configure_detail_sheet

Set up the record detail side-sheet in Airtable: enable click-to-open, define the title field, and lock or allow editing of specific fields. Uses Chrome CDP to save changes to the interface draft.

Instructions

Configures the expandable record detail side-sheet: enables record click-to-open and toggles field-level lock switches within the detail view via Chrome CDP browser automation.

When to Use

  • When setting up the opening detail card that pops out when an operational user clicks a row or Kanban card.

  • When locking audit fields, billing totals, and created dates inside the side-sheet while allowing notes or stage toggles.

  • When setting the primary header title field of the side-sheet.

When NOT to Use

  • Do NOT use this tool for high-density table column inline edit permissions. Use 'airtable_set_field_permissions' instead.

  • Do NOT use this tool to publish interface draft changes. Use 'airtable_publish_interface' instead.

Operational Disclosures

  • Prerequisites: Chrome running with '--remote-debugging-port=9223'.

  • Side Effects: Clicks into the side-sheet configuration pane and adjusts record detail layout switches.

  • Persistence: Saved to interface draft; published live using 'airtable_publish_interface'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesAirtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)
page_idNoInterface Page ID (optional if already on the target page)
cdp_portNoChrome DevTools Protocol port (default: 9223)
title_fieldNoField name to use as the hero title on the detail card (e.g. "Merchant Name")
locked_fieldsNoField names to lock from editing within the side-sheet
editable_fieldsNoField names to allow editing within the side-sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • changedInput schema / properties / base_id / description
      Previous value: -"Airtable Base ID (starts with app...)"New value: +"Airtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)"
    • changedInput schema / properties / cdp_port / description
      Previous value: -"Chrome DevTools Protocol port (default 9223)"New value: +"Chrome DevTools Protocol port (default: 9223)"
    • changedInput schema / properties / editable_fields / description
      Previous value: -"Fields inside the detail side-sheet to allow editing (Allow inline editing = ON)"New value: +"Field names to allow editing within the side-sheet"
    • changedInput schema / properties / locked_fields / description
      Previous value: -"Fields inside the detail side-sheet to lock (Allow inline editing = OFF)"New value: +"Field names to lock from editing within the side-sheet"
    • changedInput schema / properties / page_id / description
      Previous value: -"Interface Page ID (optional if already on page)"New value: +"Interface Page ID (optional if already on the target page)"
    • changedInput schema / properties / title_field / description
      Previous value: -"Field to display as main header of the side-sheet"New value: +"Field name to use as the hero title on the detail card (e.g. \"Merchant Name\")"
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses prerequisites (Chrome with --remote-debugging-port=9223), side effects (clicks into the configuration pane and adjusts layout switches), and persistence (saved to interface draft, requiring a separate publish step). This is far beyond a generic mutation statement.

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?

The description is longer than average but each labeled section earns its place: core action, usage scenarios, exclusions, prerequisites, side effects, and persistence. The main verb and resource appear in the first sentence, with supporting details structured for quick scanning.

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?

For a CDP-automation tool with no annotations and no output schema, the description covers the essential operational context: when to use, when not to use, prerequisites, side effects, and persistence behavior. The absence of return-value details is acceptable given the configuration-oriented nature of the tool.

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 description coverage is 100%, so the structured schema already documents all six parameters. The description reinforces usage with examples like 'audit fields, billing totals, and created dates' and 'primary header title field,' but it does not add materially new semantic detail beyond what the schema provides.

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?

States a specific verb and resource ('configures the expandable record detail side-sheet') and enumerates concrete capabilities: enabling click-to-open, toggling field-level lock switches, and setting the header title field. It also differentiates from sibling tools by naming excluded use cases and their alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Dedicated 'When to Use' and 'When NOT to Use' sections provide concrete scenarios and explicitly route to sibling tools: airtable_set_field_permissions for table column inline edit permissions and airtable_publish_interface for publishing draft changes. This leaves little ambiguity about when the tool should be selected.

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