Skip to main content
Glama

append_row

Adds a new row to the end of a Google Sheets spreadsheet. Specify the spreadsheet ID, sheet name, and row values to insert data.

Instructions

スプレッドシートの最後に新しい行を追加します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheetIdYesスプレッドシートのID
sheetNameYesシート名
valuesYes追加する行のデータ

Implementation Reference

  • The main handler function for the 'append_row' tool. It authenticates with Google Sheets API and appends the provided values as a new row to the specified sheet using the spreadsheets.values.append method.
    async function appendRow(
      spreadsheetId: string,
      sheetName: string,
      values: string[]
    ) {
      const authClient = await auth.getClient();
      const sheets = google.sheets({ version: "v4", auth: authClient as any });
    
      const response = await sheets.spreadsheets.values.append({
        spreadsheetId,
        range: `${sheetName}!A:Z`,
        valueInputOption: "RAW",
        requestBody: {
          values: [values],
        },
      });
    
      return {
        content: [
          {
            type: "text",
            text: `行が正常に追加されました。更新されたセル数: ${response.data.updates?.updatedCells}`,
          },
        ],
      };
    }
  • The tool definition including name, description, and input schema for 'append_row' used for tool listing and validation.
    {
      name: "append_row",
      description: "スプレッドシートの最後に新しい行を追加します",
      inputSchema: {
        type: "object",
        properties: {
          spreadsheetId: {
            type: "string",
            description: "スプレッドシートのID",
          },
          sheetName: {
            type: "string",
            description: "シート名",
          },
          values: {
            type: "array",
            items: {
              type: "string",
            },
            description: "追加する行のデータ",
          },
        },
        required: ["spreadsheetId", "sheetName", "values"],
      },
  • src/index.ts:170-175 (registration)
    The switch case in the CallToolRequestHandler that registers and dispatches to the appendRow handler when 'append_row' is called.
    case "append_row":
      return await appendRow(
        args.spreadsheetId as string,
        args.sheetName as string,
        args.values as string[]
      );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('append row') but doesn't mention whether this requires specific permissions, what happens if the spreadsheet doesn't exist, whether the operation is atomic, or what error conditions might occur. For a mutation tool with zero annotation coverage, this is insufficient.

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?

The description is a single, clear sentence in Japanese that directly states the tool's function without any unnecessary words. It's perfectly front-loaded and wastes no space on redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is too minimal. It doesn't address what happens after appending (success indicators, error responses), doesn't mention constraints or limitations, and doesn't help the agent understand how this differs from similar spreadsheet manipulation 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?

The schema description coverage is 100%, with all three parameters clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides, so it meets the baseline for adequate but not exceptional parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('append row') and target resource ('spreadsheet'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'write_sheet' or 'create_sheet', which might have overlapping functionality for spreadsheet modification.

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 provides no guidance on when to use this tool versus alternatives like 'write_sheet' or 'create_sheet'. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to guess based on tool names alone.

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/Kyohei-9841/google-spreadsheet-MCP'

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