Skip to main content
Glama

create_sheet

Add a new sheet to an existing Google Spreadsheet by specifying the spreadsheet ID and desired sheet name.

Instructions

新しいシートを作成します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheetIdYesスプレッドシートのID
sheetNameYes作成するシート名

Implementation Reference

  • The core handler function that executes the creation of a new sheet in the specified Google Spreadsheet using the Google Sheets API's batchUpdate method with an addSheet request.
    async function createSheet(spreadsheetId: string, sheetName: string) {
      const authClient = await auth.getClient();
      const sheets = google.sheets({ version: "v4", auth: authClient as any });
    
      const response = await sheets.spreadsheets.batchUpdate({
        spreadsheetId,
        requestBody: {
          requests: [
            {
              addSheet: {
                properties: {
                  title: sheetName,
                },
              },
            },
          ],
        },
      });
    
      return {
        content: [
          {
            type: "text",
            text: `シート "${sheetName}" が正常に作成されました。`,
          },
        ],
      };
    }
  • Defines the tool schema for 'create_sheet', including the name, description, and inputSchema with required parameters spreadsheetId (string) and sheetName (string). This is part of the tools array used for tool listing.
    {
      name: "create_sheet",
      description: "新しいシートを作成します",
      inputSchema: {
        type: "object",
        properties: {
          spreadsheetId: {
            type: "string",
            description: "スプレッドシートのID",
          },
          sheetName: {
            type: "string",
            description: "作成するシート名",
          },
        },
        required: ["spreadsheetId", "sheetName"],
      },
    },
  • src/index.ts:180-182 (registration)
    The switch case in the main CallToolRequestSchema handler that registers and dispatches the 'create_sheet' tool call to the createSheet function.
    case "create_sheet":
      return await createSheet(args.spreadsheetId as string, args.sheetName as string);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('creates') but doesn't cover critical traits like required permissions, whether this is a destructive operation, error handling, or what happens if a sheet with the same name exists. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence in Japanese that directly states the tool's purpose with zero wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the complexity of a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, new sheet details), error conditions, or behavioral nuances, leaving significant gaps for the agent to infer.

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 both parameters ('spreadsheetId' and 'sheetName') clearly documented in the schema. The description adds no additional meaning about the parameters beyond what the schema provides, so it meets the baseline score for high schema coverage without compensating value.

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 '新しいシートを作成します' (creates a new sheet) clearly states the verb ('creates') and resource ('sheet'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'append_row' or 'write_sheet' that might also modify sheets, so it doesn't reach the highest clarity level.

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. It doesn't mention prerequisites (e.g., needing an existing spreadsheet), exclusions (e.g., not for modifying existing sheets), or comparisons to sibling tools like 'append_row' or 'write_sheet', leaving the agent with no usage context.

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