gg-mcp

by tannht

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

export_spreadsheet

Export a Google Sheets spreadsheet to CSV, XLSX, PDF, or TSV. Select a sheet by ID; defaults to the first sheet.

Instructions

Export a spreadsheet. Formats: csv, xlsx, pdf, tsv. sheet_id: 0 for first sheet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spreadsheet_id": "<spreadsheet_id>"
    },
    "name": "export_spreadsheet"
  }
}

Input Schema

Name	Required	Default
`spreadsheet_id`	Yes
`format`	No	csv
`sheet_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Minimal behavioral disclosure. It explains sheet_id default but does not describe what 'export' means (e.g., file download, URL generation), or any permissions or side effects. No annotations to supplement.

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?

Two sentences, front-loaded with purpose, no redundant information. Every part is necessary.

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

Completeness3/5

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

For a simple export tool with 3 parameters and no output schema, the description covers the basics but lacks details on return value and parameter sources. Adequate but not thorough.

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 0%, so description carries burden. It adds meaning for format (lists options) and sheet_id (explains 0 for first sheet), but spreadsheet_id is not explained at all.

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?

Clearly states it exports a spreadsheet and lists supported formats (csv, xlsx, pdf, tsv), which is specific. However, it does not differentiate from sibling export tools like export_document or export_presentation.

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?

No guidance on when to use this tool versus other spreadsheet or export tools. Does not mention prerequisites or scenarios.

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