Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_insert_table

Inserts a data-filled table with a bolded header row into a Google Doc, either at the end of the document or at a specified index, so you can add structured content programmatically.

Instructions

Insert a table filled with data (first row = header, bolded) at the end of a Doc or at an index.

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": {
      "documentId": "<documentId>",
      "rows": "<rows>"
    },
    "name": "docs_insert_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
indexNo
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds genuine behavioral detail beyond that: the first row is treated as a header and bolded, and insertion defaults to the document end. It does not disclose whether inserting at an index shifts or overwrites existing content, nor any permission requirements.

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?

A single tight sentence with the action and the two placement behaviors front-loaded; no filler or redundant restatement of the tool name.

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 three-parameter mutation with no output schema, the description covers what gets created and where, but leaves open how index interacts with existing content and what the tool returns. Adequate but with clear gaps an agent would want filled.

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 the description carries the burden; it usefully explains that 'rows' is tabular data whose first row becomes a bolded header, and that 'index' controls placement versus the default end-of-document append. It adds nothing for 'documentId', does not clarify whether index is 0-based, and does not state the minimum row requirement or cell typing from the schema.

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?

States a specific verb and resource ('Insert a table filled with data') scoped to a Doc, which distinguishes it from siblings like docs_insert_markdown or docs_insert_image by resource type. It does not explicitly name those siblings, but the resource-specific verb is unambiguous.

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 phrase 'at the end of a Doc or at an index' implies a default append behavior, but there is no explicit when-to-use guidance and no mention of alternatives such as docs_insert_markdown or docs_batch_update for other insertion needs. The agent must infer the selection criteria.

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