Leadbase | AI B2B Lead Generation

Sheets Get

sheets_get

Read-onlyIdempotent

Get current sheet metadata, column types, stable IDs, option IDs and versions before editing an existing sheet. Preserve existing schema and data. For a newly created sheet, reuse create/add-column receipts instead of rereading known metadata; read cell values with sheets_query.

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": {
      "sheetId": "<sheetId>"
    },
    "name": "sheets_get"
  }
}

Input Schema

Name	Required	Description	Default
`sheetId`	Yes

Output Schema

Name	Required	Description	Default
`columns`	Yes
`sheetId`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026
- changedOutput schema / properties / metadata / properties / views / items / properties / columnOrder / maxItems
```
Previous value: -250New value: +1000
```
- changedOutput schema / properties / metadata / properties / views / items / properties / hiddenColumns / maxItems
```
Previous value: -250New value: +1000
```

Changed1 schema field changedOct 24, 2026

addedOutput schema / properties / columns / items / properties / typeLocked / description

Added value: +"True only while this column's own type migration is in flight. Stored cell values and unrelated enrichment do not lock the data type."

First observedOct 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered by structure. The description adds workflow context (use prior receipts for fresh sheets) and the 'preserve existing schema and data' caution, though it says nothing about auth, rate limits, or freshness guarantees.

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?

Three tight sentences, front-loaded with the primary action before alternatives. The sentence 'Preserve existing schema and data' is somewhat cryptic as an imperative and slightly blurs the otherwise crisp structure.

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?

An output schema exists, so return values needn't be explained, and the description covers purpose, timing, and sibling routing. The only soft spot is the ambiguous 'preserve existing schema and data' instruction, which is unclear about what the caller must do.

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?

Only one parameter (sheetId) with 0% schema description coverage; the description never clarifies what sheetId is beyond 'stable IDs' appearing in the metadata list. The required flag and uuid format come from the schema, so the description neither compensates nor misleads.

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 and resource ('Get current sheet metadata, column types, stable IDs, option IDs and versions') and explicitly separates itself from sheets_query, which reads cell values. An agent can distinguish it from view_sheet/sheets_list without opening any schema.

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?

Gives an explicit when ('before editing an existing sheet'), a when-not ('for a newly created sheet, reuse create/add-column receipts instead of rereading'), and names the alternative for a different need ('read cell values with sheets_query'). Nothing is left to inference.

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

All Leadbase | AI B2B Lead Generation 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.