ai-toolkit

append_sheet_row

Appends a row directly below the last populated row in a Google Sheet tab, avoiding blank gaps and misplacement from auto-detection. Use it to add data to the bottom of a sheet reliably.

Instructions

Append a single row directly below a tab's last populated row.

Placement is deterministic: the tool reads the tab, takes the row after the last one holding any value, and writes there starting at column A. It does not use the Sheets API's table auto-detection, which misplaced rows on real trackers (blank gap rows, a blank first cell, tab titles with spaces). If the grid is full it is grown first. To write anywhere other than the bottom, use update_sheet_range or insert_sheet_rows.

sheet_id is the target spreadsheet's ID (the long token in its URL, .../spreadsheets/d/<sheet_id>/edit); it is required, so confirm which sheet to write to per call rather than assuming a default. values is the ordered list of cell values for the new row — read the header row first so this lines up with the existing columns. value_input_option USER_ENTERED parses dates/numbers/formulas like typing; RAW stores text verbatim. Returns the range that was written.

Input Schema

TableJSON Schema

Name	Required	Default
`tab`	No	Sheet1
`values`	Yes
`sheet_id`	Yes
`value_input_option`	No	USER_ENTERED

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavior: deterministic placement, does not use auto-detection, grows grid if full, returns written range. No hidden surprises.

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

Conciseness5/5

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

Description is well-structured with purpose front-loaded, followed by placement logic, alternatives, and parameter details. Each sentence adds value, no fluff.

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?

Complete for a mutation tool with no annotations: covers placement behavior, grid growth, parameter details, alternatives, and return value. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0%, so description must explain parameters. It explains sheet_id (required, from URL), values (ordered list, align with columns), and value_input_option (USER_ENTERED vs RAW). Tab is implied but not explicitly described; still clear from context.

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 (append) and resource (a single row to a tab), with precise placement logic. Differentiates from update_sheet_range and insert_sheet_rows by naming them as alternatives.

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?

Explicitly states when to use this tool (to append at bottom) and when not to (to write elsewhere, use update_sheet_range or insert_sheet_rows). Also advises reading the header row first for alignment.

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