Skip to main content
Glama

update_dropdown_options_tool

Manage dropdown options in a Google Sheets table column by adding or removing specific choices. Provide spreadsheet, sheet, table, column, and action to update.

Instructions

Update dropdown options in a table column.

This tool can add or remove specific dropdown options from an existing column in a table.
For 'add' action: Adds new options to existing dropdown (preserves existing options).
For 'remove' action: Removes specific options from existing dropdown.

Args:
    spreadsheet_name: Name of the spreadsheet
    sheet_name: Name of the sheet containing the table
    table_name: Name of the table to update dropdown options in
    action: Action to perform - "add" or "remove"
    column_name: Name of the column to update dropdown options for
    dropdown_options: List of dropdown options to add/remove

Returns:
    JSON string with success status and dropdown update details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_nameYesThe name of the Google Spreadsheet
sheet_nameYesThe name of the sheet containing the table
table_nameYesName of the table to update dropdown options in
actionYesAction to perform: 'add' or 'remove'
column_nameYesName of the column to update dropdown options for
dropdown_optionsNoList of dropdown options to add/remove (required for 'add' and 'remove' actions)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that add preserves existing options and remove deletes specific options, but does not mention potential side effects (e.g., impact on existing data) or authentication needs.

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 front-loaded with purpose and structured with Args/Returns, but includes some redundancy (e.g., repeating parameter types). Could be slightly more concise.

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?

Given the tool's complexity (6 parameters, output schema provided), the description covers all necessary aspects: actions, parameter usage, and return format. No missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage, baseline is 3. Description adds value by explaining the effect of actions on dropdown options (e.g., 'preserves existing options'), which goes beyond schema descriptions.

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 'Update dropdown options in a table column' and specifies add/remove actions, distinguishing it from sibling tools that add/delete columns or 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?

The description provides clear context for when to use add vs remove actions but does not explicitly state when not to use this tool or compare with alternatives.

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