Skip to main content
Glama
Praroop1435

Airtable Full-Stack MCP

by Praroop1435
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

airtable_create_interface_page

Builds a new Interface Designer page in an Airtable base—dashboard, kanban, grid, or record review—so end users can interact with table data without raw database access.

Instructions

Creates a new Interface Designer page (Dashboard, Kanban, Grid, or Record Review) inside an Airtable base using Chrome DevTools Protocol (CDP) browser automation.

When to Use

  • When building frontend web interfaces for your Airtable base so non-technical users or clients can interact with data without touching raw tables.

  • When creating an Executive Dashboard with KPI summary cards, a Kanban board stacked by status, or a high-density Review Queue.

  • When expanding an existing interface application with a new page.

When NOT to Use

  • Do NOT use this tool to create backend database tables or columns. Use 'airtable_create_base_schema' or 'airtable_modify_schema' instead.

  • Do NOT use this tool to configure Kanban stacking options on an existing page. Use 'airtable_configure_kanban' instead.

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

Operational Disclosures

  • Prerequisites: Requires Google Chrome running locally with remote debugging enabled (e.g. '--remote-debugging-port=9223') and an active Airtable login session.

  • Side Effects: Automatically opens or switches to the base's Interface Designer in Chrome, toggles Edit Mode, and creates a draft page.

  • Persistence: Changes remain in draft state until published using 'airtable_publish_interface'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesAirtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)
cdp_portNoChrome DevTools Protocol port (default: 9223 or AIRTABLE_CDP_PORT)
page_nameYesDisplay name for the new interface page (e.g. "Merchant Pipeline", "Executive Overview")
table_nameYesSource table name feeding records to this interface page
layout_typeYesInterface page archetype: "dashboard" (KPI metrics), "kanban" (status cards), "grid" (tabular sheet), "record_review" (split master-detail queue)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 or AIRTABLE_CDP_PORT)"New value: +"Chrome DevTools Protocol port (default: 9223 or AIRTABLE_CDP_PORT)"
    • changedInput schema / properties / layout_type / description
      Previous value: -"Interface archetype layout"New value: +"Interface page archetype: \"dashboard\" (KPI metrics), \"kanban\" (status cards), \"grid\" (tabular sheet), \"record_review\" (split master-detail queue)"
    • changedInput schema / properties / page_name / description
      Previous value: -"Display name for the new interface page"New value: +"Display name for the new interface page (e.g. \"Merchant Pipeline\", \"Executive Overview\")"
    • changedInput schema / properties / table_name / description
      Previous value: -"Source table name for this page data"New value: +"Source table name feeding records to this interface page"
  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 clearly discloses prerequisites (Chrome with remote debugging, active Airtable session), side effects (opens Interface Designer, toggles Edit Mode, creates draft), and persistence (draft until published). This is exemplary behavioral transparency.

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 well-structured with clear headers, front-loads the core action, and every section earns its place. It is detailed but not bloated, and the formatting makes it easy for an agent to parse.

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 the tool's complexity (CDP browser automation, draft workflow, prerequisites), the description covers all necessary operational context: prerequisites, side effects, persistence, and exclusions. No critical information is missing for correct invocation.

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 baseline is 3. The description does not add parameter-level detail beyond the schema, but it does contextualize layout_type and the CDP dependency. Since the schema already documents every parameter thoroughly, this is adequate.

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 ('Creates') and resource ('Interface Designer page') and enumerates the exact page types (Dashboard, Kanban, Grid, Record Review). It clearly distinguishes this tool from siblings by naming what it does not do and pointing to 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?

The 'When to Use' and 'When NOT to Use' sections explicitly state appropriate contexts and name the alternative tools for excluded cases, such as airtable_create_base_schema and airtable_configure_kanban. This leaves no ambiguity about when to select this tool.

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