Skip to main content
Glama
Praroop1435

Airtable Full-Stack MCP

by Praroop1435
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

airtable_rebrand_interface

Rebrand an Airtable interface by renaming the top header title and sidebar navigation folder bundle. Organize sidebar pages into logical groups for a client or department.

Instructions

Renames the top-level interface brand title and sidebar navigation folder bundle via double-click CDP automation.

When to Use

  • When customizing an interface for a specific client brand, department, or internal application name (e.g. changing 'Untitled interface' to 'Vape Runners Merchant Portal').

  • When organizing sidebar pages into logical folders or bundles.

When NOT to Use

  • Do NOT use this tool to rename tables or fields. Use 'airtable_modify_schema' instead.

  • Do NOT use this tool to create new interface pages. Use 'airtable_create_interface_page' instead.

Operational Disclosures

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

  • Side Effects: Selects and double-clicks the interface header title element and/or sidebar group label, committing new string values.

  • Persistence: Saved to interface draft; must be published to become visible to end-users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew display title for the top interface header banner
base_idYesAirtable Base ID (starts with app, e.g. appoorUuG6wgx8dJ1)
cdp_portNoChrome DevTools Protocol port (default: 9223)
sidebar_bundle_nameNoNew title for the sidebar page navigation folder bundle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / sidebar_bundle_name / description
      Previous value: -"New name for the sidebar page group/folder"New value: +"New title for the sidebar page navigation folder bundle"
    • changedInput schema / properties / title / description
      Previous value: -"New title for the interface header"New value: +"New display title for the top interface header banner"
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and delivers: prerequisites (Chrome on port 9223), side effects (selects/double-clicks elements, commits strings), and persistence (saved to draft, must publish). This is more than most tool definitions provide.

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?

Well-structured with headers and bullets; every sentence adds operational value. The main action is front-loaded, and the sections are scannable.

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 prerequisites, side effects, persistence, and exclusions, which is strong for a no-annotation, no-output-schema tool. It doesn't state what happens when only base_id is provided (both optional fields omitted) or how to verify success, so a small gap remains.

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 coverage is 100%, so baseline is 3. The description adds context for title and sidebar_bundle_name in the purpose line, but does not elaborate on cdp_port or base_id beyond the schema. It also doesn't clarify that title and sidebar_bundle_name are optional in combination.

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 opening sentence names a specific verb ('Renames'), the exact resource ('top-level interface brand title and sidebar navigation folder bundle'), and the mechanism ('double-click CDP automation'). It clearly differentiates from siblings by explicitly saying what it is not for.

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 give concrete scenarios and explicitly route to airtable_modify_schema and airtable_create_interface_page. 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