google-workspace-mcp-advanced

find_and_replace_doc

Replace all instances of a word or phrase in a Google Doc with new text, supporting case sensitivity and a preview mode to review changes before finalizing.

Instructions

Finds and replaces text throughout a Google Doc.

Args: user_google_email: User's Google email address document_id: ID of the document to update find_text: Text to search for replace_text: Text to replace with match_case: Whether to match case exactly dry_run: When True (default), return planned mutation without executing it

Returns: str: Confirmation message with replacement count

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>",
      "find_text": "<find_text>",
      "replace_text": "<replace_text>"
    },
    "name": "find_and_replace_doc"
  }
}

Input Schema

Name	Required	Description	Default
`user_google_email`	Yes
`document_id`	Yes
`find_text`	Yes
`replace_text`	Yes
`match_case`	No
`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

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It explains the dry_run behavior and return value, but does not disclose potential side effects like formatting changes or auth requirements beyond the email parameter.

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 a single sentence followed by a structured Args/Returns section. It is clear and efficient, though the Args section could be slightly more concise.

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?

With 6 parameters, no nested objects, and an output schema, the description covers the core behavior (find and replace) and the dry_run feature. It lacks details on prerequisites or regex support, but is sufficient for basic use.

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?

Schema covers 0% of parameter descriptions, but the Args section provides brief explanations for all 6 parameters (e.g., 'Text to search for'). This adds meaning beyond the schema structure.

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 action 'finds and replaces text' and the resource 'Google Doc'. It distinguishes itself from sibling tools like 'modify_doc_text' through the explicit find-and-replace mechanism.

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 includes a dry_run parameter that defaults to True, indicating the tool can be used safely for previewing changes. However, it does not explicitly contrast with alternatives like 'modify_doc_text' or provide when-not-to-use guidance.

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

Deploy Server