Skip to main content
Glama

get_table_metadata_tool

Retrieve comprehensive metadata for Google Sheets tables, including structure, columns, data types, formatting, and statistics. Optionally include sample data or formulas.

Instructions

Get comprehensive metadata for tables in Google Sheets.

This tool provides detailed information about table structure, columns, data types,
formatting, statistics, and other properties. If no table name is provided, returns 
metadata for all tables.

Args:
    spreadsheet_name: Name of the spreadsheet
    sheet_name: Name of the sheet containing the table
    table_name: Name of the table to get metadata for (optional)
    include_sample_data: Whether to include sample data rows
    include_formulas: Whether to include formula information
    include_formatting: Whether to include cell formatting details
    include_statistics: Whether to include data statistics
    max_sample_rows: Maximum number of sample rows to return
    specific_columns: List of column names to get metadata for (optional)
    exclude_metadata_types: List of metadata types to exclude

Returns:
    JSON string containing table metadata or list of all tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_nameYesThe name of the Google Spreadsheet
sheet_nameYesThe name of the sheet containing the table
table_nameNoName of the table to get metadata for. If not provided, returns metadata for all tables in the sheet.
include_sample_dataNoWhether to include sample data rows
include_formulasNoWhether to include formula information
include_formattingNoWhether to include cell formatting details
include_statisticsNoWhether to include data statistics
max_sample_rowsNoMaximum number of sample rows to return
specific_columnsNoList of column names to get metadata for (optional)
exclude_metadata_typesNoList of metadata types to exclude (e.g., ['sample_data', 'formatting', 'statistics', 'merges', 'conditional_formatting', 'filters'])

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so the description carries full burden. It implies read-only behavior with 'Get metadata', but does not explicitly confirm it does not modify data. The return format is mentioned but lacks details on error conditions or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise, with a clear overview and structured Args/Returns. However, the Args section is verbose and redundantly lists parameters, increasing length without adding new information.

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?

Given the tool's complexity (10 params, output schema exists), the description covers parameter usage, behavior for optional inputs, and return type. It lacks explicit error handling notes or limits, but is generally complete for effective usage.

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 coverage is 100%, so all parameters already have descriptions. The description's Args section largely duplicates the schema, adding marginal value. It clarifies the optional nature of table_name and sample data inclusion, but does not provide deeper semantics beyond the schema.

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?

The description clearly states it gets comprehensive metadata for tables in Google Sheets, specifying verb+resource (get metadata) and scope (tables in spreadsheet/sheet). It distinguishes from siblings like get_table_data_tool by focusing on structure, columns, and statistics rather than raw cell values.

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?

The description provides clear context: use when detailed table structure is needed, and explains behavior when table_name is omitted (returns all tables). However, it does not explicitly say when not to use or mention alternative tools, leaving some ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henilcalagiya/google-sheets-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server