Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by tom275275
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_doc_tab

Rename a tab in a Google Doc by providing the document ID, tab ID, and new title. Organize document structure with a direct API call.

Instructions

Renames a tab in a Google Doc.

Args: user_google_email: User's Google email address document_id: ID of the document to update tab_id: ID of the tab to rename (use inspect_doc_structure to find tab IDs) title: New title for the tab

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>",
      "tab_id": "<tab_id>",
      "title": "<title>"
    },
    "name": "update_doc_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
tab_idYes
document_idYes
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.3

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does state the mutating behavior ('Renames') and the return value (confirmation message with document link), but it does not mention authorization requirements, failure conditions, or edge cases. This is reasonable for a simple rename operation but not fully transparent.

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 compact and well-structured with a purpose sentence followed by Args and Returns sections. Every line serves a purpose, and the format makes it easy for an agent to scan and extract the needed information quickly.

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

Completeness5/5

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

For a simple four-string-parameter rename operation, this description is complete: it explains the action, all parameters, a discovery method for tab_id, and the return value. Given the lack of annotations, it provides enough detail for an agent to invoke the tool correctly without additional inference.

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 input schema provides no descriptions for any of the four parameters, but the description documents each one meaningfully. It also adds a valuable cross-reference for tab_id, telling the agent to use inspect_doc_structure to discover valid tab IDs, fully compensating for the schema's lack of detail.

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 line, 'Renames a tab in a Google Doc,' states a specific verb, resource, and operation. It clearly distinguishes this tool from siblings like insert_doc_tab and delete_doc_tab, and its scope is obvious even among the many Google-doc-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operating context and explicitly points users to inspect_doc_structure for finding tab IDs, which is valuable guidance. It does not explicitly enumerate when not to use the tool or compare against insert_doc_tab/delete_doc_tab, so it falls just short of a perfect usage-guideline score.

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