google-workspace-mcp

docs_insert_image

Insert images into Google Docs from a URL, with optional positioning and size adjustments.

Instructions

Insert an image into a Google Doc from a URL.

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": {
      "document_id": "<document_id>",
      "image_uri": "<image_uri>"
    },
    "name": "docs_insert_image"
  }
}

Input Schema

Name	Required	Description	Default
`index`	No
`width_pt`	No
`height_pt`	No
`image_uri`	Yes
`document_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the primary function and does not disclose key behaviors such as URL accessibility requirements, default placement, whether the image is embedded or linked, or what happens on invalid URLs. This is a significant gap for a mutation tool.

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, front-loaded sentence with no wasted words. It is concise and easy to parse, though it sacrifices informativeness for brevity.

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

Completeness2/5

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

Given the complexity of the tool (inserting an image into a specific document with size and positioning parameters) and the lack of annotations or schema descriptions, the description is insufficient. It does not explain placement semantics, prerequisites for the URL, or how the index parameter affects behavior. The presence of an output schema does not compensate for these gaps in selection and invocation guidance.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'from a URL' which sheds light on image_uri, but it does not explain document_id, index, width_pt, or height_pt. Most parameter meanings remain opaque, requiring the agent to guess or use defaults without clear guidance.

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 specific action (insert), the resource (image), the destination (Google Doc), and the source (URL). This distinguishes it from sibling tools like docs_insert_text or slides_insert_image.

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 when to use this tool (when inserting an image from a URL into a Google Doc) but provides no explicit alternatives or exclusions. It does not differentiate from similar insert tools in other services (e.g., slides_insert_image) or other docs inserts.

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

Deploy Server