Niches · Spreadsheets & operational tables
Read a sheet or table so the agent can answer from it
Four or more companies' docs show a full fit.
What counts as done
Every requested row returned as typed values with column names (or field ids), paged, with the file found by name.
Measured, for our own tests: no single response exceeds about 10,000 tokens, and the file is found in at most two calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: what's in the jobs sheet
, summarise this spreadsheet
, how much did we spend on subscriptions
, read the leads table
Does the job 7
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Airtable BB Formagrid Inc (doing business as Airtable) | List bases returns names and Get base schema returns table and field names and ids, so a named table is found in two calls. List records pages at pageSize up to 100 with an offset and returnFieldsByFieldId; values come back typed JSON. source |
| Baserow C Baserow B.V. | GET /api/database/tables/all-tables/ lists every table a database token can reach by name, then list rows pages with page and size, user_field_names for column names, and {link_field}__join to pull fields from linked rows. source |
| Coda (Superhuman Docs) BB Superhuman Platform Inc. (parent of Coda Project LLC) | GET /docs takes a query to find a doc by name and GET /docs/{id}/tables lists tables, then rows page with limit and pageToken, with useColumnNames and valueFormat for typed values. X-Coda-Doc-Version: latest guards against a stale snapshot. source |
| Microsoft Excel (Microsoft Graph workbook API) D Microsoft Corporation | drive/root/search(q=...) finds the workbook by name, then GET .../tables/{name}/rows pages with $top and $skip, and columns come from the table header; values are JSON cell values. source |
| NocoDB BB NocoDB Inc (doing business as NocoDB) | List bases and List tables return titles, then List Table Records pages with page, pageSize or limit and offset (100 a page on Cloud), with fieldIdOnResult for stable field ids and nested linked records up to nestedLimit. source |
| SeaTable B SeaTable GmbH | A Base-Token is bound to one base, Get Metadata returns its tables and columns by name, and List Rows takes table_name, view_name, start and limit; the SQL endpoint returns typed rows with column metadata. source |
| Smartsheet API + MCP B Smartsheet Inc. | GET /search with query or GET /sheets finds a sheet by name, then GET /sheets/{id} pages with page and pageSize, narrows with columnIds, and returns typed cells keyed by column id with titles in the column list. source |
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Google Sheets API A Google LLC | Files open by id only; finding one by name needs Drive files.list with name contains, and acc-11's agent couldn't find a sheet without it. values.get has no row paging, so large tables need split A1 ranges; acc-28 shows merged cells carry only the first value. source |
| Grist E Grist Labs Inc. | GET /orgs/{org}/workspaces lists documents by name and GET /docs/{id}/tables lists tables, then /records returns typed values by column id. Records take limit but no offset (acc-18, open), so paging means falling back to the SQL endpoint with LIMIT and OFFSET. source |
| Teable B Teable AI, Inc. | GET /space/{id}/search finds bases and tables by name, and list records pages with take (up to 1,000) and skip or a cursor, with fieldKeyType=id. acc-23 (open) shows link fields return only id and title, so linked values cost extra calls. source |
What stops agents finishing
- the file can only be opened by id and the user gives a name
- no paging, so a large table floods context
- token reaches every file the user owns
Around it
Before: file-storage.find-file. After: data.analyse, document-extraction.summarise.
Where this comes from
Weight 28 of 100 in Spreadsheets & operational tables: 10 of 35 accounts; the most common job across HN (finance sheets, pull-and-push CLI, Grist via API) and the Grist and Teable read issues
The same as data: /api/v1/use-cases/spreadsheets.read-table.json, or the MCP tool get_use_case with id spreadsheets.read-table. Other jobs in this category: /api/v1/niches?category=spreadsheets.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.