google-workspace-mcp-advanced

update_doc_headers_footers

Update headers or footers in a Google Doc with options for default, first page only, or even page types. Supports dry run to preview changes before applying.

Instructions

Updates headers or footers in a Google Doc.

Args: user_google_email: User's Google email address document_id: ID of the document to update section_type: Type of section to update ("header" or "footer") content: Text content for the header/footer header_footer_type: Type of header/footer ("DEFAULT", "FIRST_PAGE_ONLY", "EVEN_PAGE") dry_run: When True (default), return planned mutation without executing it

Returns: str: Confirmation message with update details

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>",
      "section_type": "<section_type>",
      "content": "<content>"
    },
    "name": "update_doc_headers_footers"
  }
}

Input Schema

Name	Required	Default
`user_google_email`	Yes
`document_id`	Yes
`section_type`	Yes
`content`	Yes
`header_footer_type`	No	DEFAULT
`dry_run`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jun 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must bear full responsibility for behavioral disclosure. It does not mention side effects (e.g., overwriting existing content), permissions required, or whether the operation is reversible. The dry_run parameter is helpful but insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured as a docstring with distinct sections (short summary, Args, Returns). It avoids redundancy and is front-loaded with the core purpose. Minor improvement would be to condense parameter lines.

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?

Given 6 parameters, no annotations, and the presence of an output schema, the description provides adequate guidance for typical use but lacks details on error handling, access requirements, or interaction with existing headers/footers. The dry_run parameter adds some completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description provides brief but meaningful explanations for each parameter, including the acceptable values for 'header_footer_type'. This adds significant value over 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 description clearly states the verb ('Updates') and the resource ('headers or footers in a Google Doc'), specifying exactly what the tool does. It is distinct from sibling tools like 'update_google_doc' which imply broader document changes.

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 provides no explicit guidance on when to use this tool versus alternatives like 'batch_update_doc' or 'insert_doc_elements'. There is no mention of prerequisites or conditions for use, leaving the agent to infer context.

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

Deploy Server