Teable MCP (Official)

list-bases

Read-onlyIdempotent

List the projects (bases) the caller can access, with their IDs, names, spaces and the caller's role, one page at a time. Call this first to find the baseId other tools need; pass search or spaceId to find a specific base instead of paging through everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-bases"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size (default 50, max 100). Follow nextOffset while hasMore is true.
`offset`	No	Bases to skip (default 0).
`search`	No	Case-insensitive match on the base name or ID. Narrows the list before paging.
`spaceId`	No	Only list bases in this space, e.g. "spcXXXXXXXX".

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Page size (default 50, max 100). Follow nextOffset while hasMore is true.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Bases to skip (default 0).",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Case-insensitive match on the base name or ID. Narrows the list before paging.",
+  "type": "string"
+}

addedInput schema / properties / spaceId

Added value: +{
+  "description": "Only list bases in this space, e.g. \"spcXXXXXXXX\".",
+  "type": "string"
+}

First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds real context by noting results are access-scoped to the caller and returned 'one page at a time'. Pagination mechanics are partly deferred to the schema, and no rate limits or result-size caveats are given.

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?

Two sentences, front-loaded with the core purpose and followed by the actionable usage rule. No filler, no repetition of annotation or schema content beyond what supports routing.

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?

There is no output schema, so the description carries the burden of describing return values, and it does (IDs, names, spaces, role). Combined with the schema's paging fields and the annotations' read-only profile, an agent has everything needed to call this correctly.

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 limit, offset, search and spaceId are already documented with defaults and formats. The description reinforces the search/spaceId narrowing intent, which is a useful but marginal addition over the schema (baseline 3).

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 (List) and resource (projects/bases) and enumerates the returned fields (IDs, names, spaces, caller's role). It also clarifies the terminology mapping 'projects (bases)', so an agent can distinguish this discovery tool from the record-level siblings like get-records or create-records.

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

Usage Guidelines4/5

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

Explicitly says 'Call this first to find the baseId other tools need', giving a clear ordering rule, and offers an alternative strategy: pass search or spaceId instead of paging through everything. It doesn't name any sibling tools or state when not to use it, which keeps it short of a 5.

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?