Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by tom275275
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

insert_doc_tab

Add a new tab to a Google Doc at a chosen index, with optional nesting under a parent tab. Provide user email, document ID, title, and index to update the document structure.

Instructions

Inserts a new tab into a Google Doc.

Args: user_google_email: User's Google email address document_id: ID of the document to update title: Title of the new tab index: Position index for the new tab (0-based among sibling tabs) parent_tab_id: Optional ID of a parent tab to nest the new tab under

Returns: str: Confirmation message with document link

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": {
      "user_google_email": "<user_google_email>",
      "document_id": "<document_id>",
      "title": "<title>",
      "index": "<index>"
    },
    "name": "insert_doc_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
titleYes
document_idYes
parent_tab_idNo
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.3

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It clearly states that the operation inserts a tab, explains the 0-based indexing semantics, and notes optional parent nesting, which is useful. However, it does not disclose side effects on existing tabs, permission or authentication requirements, or failure behavior for invalid index or parent_tab_id values.

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 well organized with a clear one-line purpose, a structured Args list, and a Returns statement. Every sentence serves a purpose, and the most important action is front-loaded without any redundant filler.

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

Completeness4/5

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

Given there is no schema-level parameter documentation and no annotations, the description does a strong job of covering the essential invocation details: purpose, all parameters, and return shape. It is slightly incomplete because it omits authentication prerequisites, behavior on invalid inputs, and interaction with sibling tab operations, but the core calling contract is well defined and the output schema exists.

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?

The schema provides no property descriptions (0% coverage), so the description is entirely responsible for parameter meaning. It successfully explains all five parameters, including the crucial details that index is 0-based among sibling tabs and that parent_tab_id optionally nests the new tab, going far beyond the raw schema.

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?

The opening sentence, 'Inserts a new tab into a Google Doc,' uses a specific verb and resource, making the tool's function immediately clear. It is readily distinguishable from sibling tools like update_doc_tab, delete_doc_tab, and insert_doc_elements because the action and target are explicit.

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 explains what the tool does and lists its arguments, but it gives no explicit guidance about when to choose this tool over alternatives such as update_doc_tab or delete_doc_tab. No when-to-use, prerequisites, or exclusion conditions are stated, leaving the agent to infer usage context from the action alone.

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

Deploy Server

Other Tools