airtable-mcp-server

Describe Table

describe_table

Read-only

Retrieve detailed schema information for a specific Airtable table by base and table ID, including fields, views, types, and configurations.

Instructions

Get detailed information about a specific table

Input Schema

Name	Required	Description	Default
`baseId`	Yes	The ID of the base
`tableId`	Yes	The ID or name of the table
`detailLevel`	No	Detail level for table information: - tableIdentifiersOnly: table IDs and names - identifiersOnly: table, field, and view IDs and names - full: complete details including field types, descriptions, and configurations Note for LLMs: To optimize context window usage, request the minimum detail level needed: - Use 'tableIdentifiersOnly' when you only need to list or reference tables - Use 'identifiersOnly' when you need to work with field or view references - Only use 'full' when you need field types, descriptions, or other detailed configuration If you only need detailed information on a few tables in a base with many complex tables, it might be more efficient for you to use list_tables with tableIdentifiersOnly, then describe_table with full on the specific tables you want.	full

Output Schema

Name	Required	Description	Default
`table`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.14.0Oct 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing beyond the name: no note on what 'detailed information' contains (fields, views, configurations), no cost/rate context, no behavior of the detailLevel default. Minimal added value.

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?

A single front-loaded sentence with no waste. It is appropriately sized for a simple read tool, though it is thin rather than efficient in the sense of conveying extra value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the input schema is fully documented, so return-value and parameter gaps are covered elsewhere. What is missing is sibling differentiation and any hint of when to prefer this over list_tables, which the description leaves entirely to the schema.

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%, and the detailLevel enum is extensively documented in the schema, including LLM-specific guidance. Baseline 3 applies since the schema carries the parameter burden and the description adds no parameter meaning of its own.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get detailed information about a specific table'), which is clearer than a tautology. However, it offers no differentiation from the sibling list_tables, so an agent must infer the boundary between listing and describing tables.

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

Usage Guidelines2/5

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

The description itself gives no when-to-use or when-not-to-use guidance and never mentions list_tables. The routing advice ('use list_tables with tableIdentifiersOnly, then describe_table with full') lives entirely in the detailLevel schema description, not in the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server