Teable MCP (Official)

by ai.teable.mcp

Overview Discussions Admin

get-tables-meta

Read-onlyIdempotent

Get tables metadata in a project.

Parameters:

baseId (required): The project ID
tableId (optional): Filter by specific table ID
tableName (optional): Filter by specific table name

Returns table information:

id: Unique table identifier
name: Display name
dbTableName: Database table name (use this for SQL queries)
description: Table description
icon: Table icon

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "baseId": "<baseId>"
    },
    "name": "get-tables-meta"
  }
}

Input Schema

Name	Required	Description
`baseId`	Yes	The project (base) ID, e.g. "bseXXXXXXXX". Use list-bases to find it.
`tableId`	No	Optional: filter by specific table ID
`tableName`	No	Optional: filter by specific table name

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine value by listing the returned fields and flagging that dbTableName should be used for SQL queries, connecting it to the sql-query sibling; it omits pagination or empty-result behavior.

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?

Front-loaded purpose sentence followed by tight parameter and return lists; every line is scannable. Some redundancy with the schema's parameter descriptions keeps it from a 5.

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?

There is no output schema, so spelling out the six returned fields is necessary and well done. Only minor gaps remain, such as behavior when no tables match or when both tableId and tableName are supplied.

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 all three parameters are already documented, and the description largely restates them (baseId = project ID, optional filters). Marginal added value only, which fits the baseline 3.

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 tables metadata") scoped to a project, which distinguishes it from get-fields and get-records among siblings. It doesn't explicitly name a differentiating sibling, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the required baseId and optional tableId/tableName filters, but there is no explicit statement of when to use this versus get-fields or list-bases. The routing hint to list-bases lives only in the schema, not the description.

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

All Teable MCP (Official) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?