Skip to main content
Glama

create_table_tool

Creates a structured table in Google Sheets with custom columns, data types, and dropdown validation for organized data entry.

Instructions

Create a new table in Google Sheets.

This tool creates a structured table with specified columns and data types.
Tables provide better data organization, validation, and formatting capabilities.

Args:
    spreadsheet_name: Name of the spreadsheet
    sheet_name: Name of the sheet to create table in
    table_name: Name for the table
    start_cell: Starting cell for the table (e.g., "A1")
    column_names: List of column names
    column_types: List of column types corresponding to column_names
    dropdown_columns: List of column names that should have dropdown validation
    dropdown_values: List of comma-separated dropdown options for each dropdown column

Returns:
    JSON string with success status and table details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_nameYesThe name of the Google Spreadsheet
sheet_nameYesThe name of the sheet to create table in
table_nameYesA descriptive name for the table (e.g., 'Project Tracker', 'Customer Data')
start_cellYesStarting cell for the table (e.g., 'A1')
column_namesYesList of column names (e.g., ['Employee Name', 'Age', 'Department', 'Salary'])
column_typesYesList of column types: DOUBLE, CURRENCY, PERCENT, DATE, TIME, DATE_TIME, TEXT, BOOLEAN, DROPDOWN
dropdown_columnsNoList of column names that should have dropdown validation
dropdown_valuesNoComma-separated dropdown options for each dropdown column

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover all behavioral aspects. It discloses that this tool creates a new table and mentions data validation and formatting, but it does not specify potential side effects, permission requirements, or error conditions (e.g., if the table already exists).

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?

The description is reasonably concise with 5 sentences plus Args/Returns. It front-loads the main purpose. However, the Args list repeats schema information, which could be trimmed.

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 has 8 parameters (6 required) and an output schema, the description covers the core functionality and parameters. It mentions return value format but lacks detail on how to interpret the JSON response. It also misses usage context relative to sibling tools.

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 the baseline is 3. The description's Args section provides brief parameter explanations that largely mirror the schema. It does not add significant new meaning beyond what the schema already offers.

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 'Create a new table in Google Sheets' and explains it creates a structured table with columns and data types. It also mentions benefits like data organization and validation, distinguishing it from siblings that modify or delete tables.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this tool versus alternatives like create_sheets_tool or add_table_column_tool. There is no guidance on prerequisites or when not to use it.

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