google-workspace-mcp-advanced

insert_doc_image

Insert images into Google Docs from Drive or URLs. Set position, width, and height.

Instructions

Inserts an image into a Google Doc from Drive or a URL.

Args: user_google_email: User's Google email address document_id: ID of the document to update image_source: Drive file ID or public image URL index: Position to insert image (0-based) width: Image width in points (optional) height: Image height in points (optional) dry_run: When True (default), return planned mutation without executing it

Returns: str: Confirmation message with insertion 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>",
      "image_source": "<image_source>",
      "index": "<index>"
    },
    "name": "insert_doc_image"
  }
}

Input Schema

Name	Required	Description	Default
`user_google_email`	Yes
`document_id`	Yes
`image_source`	Yes
`index`	Yes
`width`	No
`height`	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

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions the dry_run parameter and returns a confirmation message, indicating mutation behavior. However, it lacks disclosure of required permissions, image size limits, or handling of invalid sources.

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 structured with a concise summary line and an Args list, efficiently conveying key information. It maintains clarity without unnecessary verbosity, earning its sentences.

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 no annotations and no output schema, the description covers core functionality and parameters but misses details like required permissions, image type/size constraints, and dry_run behavior (e.g., what 'planned mutation' includes). It is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description's Args section compensates well, explaining each parameter's purpose (e.g., user_google_email, image_source, index). It adds meaning beyond the schema's type definitions, though it could clarify image_source format further.

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 explicitly states it inserts an image into a Google Doc from Drive or a URL, providing a specific verb, resource, and source distinction. This differentiates from siblings like insert_doc_elements, which may handle other elements.

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

Usage Guidelines3/5

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

The description implies usage for inserting images but does not provide explicit guidance on when to use this tool vs alternatives (e.g., insert_doc_elements) or when not to use it. No exclusions or context are given.

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

Deploy Server