Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_doc_tab

Rename a Google Doc tab by providing its ID and new title. Only the display title is updated; content remains unchanged.

Instructions

Rename an existing tab in a Google Doc.

Changes the tab's display title only — does not move or delete its content. For creating tabs use insert_doc_tab; for deleting use delete_doc_tab. Requires the documents OAuth scope.

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
user_google_emailYesThe user's Google email address (authenticated account).
document_idYesTarget document ID.
tab_idYesTab ID from list_doc_tabs.
titleYesNew display title.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • changedInput schema / properties / document_id / description
      Previous value: -"ID of the document to update"New value: +"Target document ID."
    • changedInput schema / properties / tab_id / description
      Previous value: -"ID of the tab to rename (use inspect_doc_structure to find tab IDs)"New value: +"Tab ID from list_doc_tabs."
    • changedInput schema / properties / title / description
      Previous value: -"New title for the tab"New value: +"New display title."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"User's Google email address"New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses that the tool only changes the display title and does not move or delete content, and mentions required OAuth scope. This is transparent and aligns with expected behavior.

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 two sentences, front-loaded with the primary action, and contains no redundant information. Every sentence adds value.

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?

Given the simplicity of the tool (rename only) and the presence of an output schema, the description covers purpose, behavior, limitations, OAuth scope, and differentiation adequately. No missing context.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no further meaning beyond the schema's parameter descriptions, which are already clear.

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 description clearly states 'Rename an existing tab' and specifies the action is limited to changing the display title. It distinguishes from sibling tools insert_doc_tab and delete_doc_tab by explicitly naming them for creation and deletion.

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

Usage Guidelines5/5

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

The description explicitly provides guidance on when to use this tool (rename) and when not to, referring to insert_doc_tab for creation and delete_doc_tab for deletion, offering clear alternatives.

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