Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by tom275275
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

insert_doc_image

Add images to Google Docs at a specific position by providing a Drive file ID or public URL, with optional 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)

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

NameRequiredDescriptionDefault
indexYes
widthNo
heightNo
document_idYes
image_sourceYes
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.3

TDQS

B3.4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral disclosure burden. It indicates mutation through 'inserts' and mentions a confirmation return, but it does not disclose authorization requirements, side effects on document content as a result of insertion, or behavior on invalid image sources. For a mutation tool this is a notable gap.

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 tightly organized with a one-sentence summary, a straightforward arg list, and a return statement. There is no filler or duplication of schema details that aren't already present. The opening sentence front-loads the core purpose.

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?

The parameter documentation is strong, but the description omits context that would help an agent decide when to choose this tool over insert_doc_elements, and it does not mention whether authenticated user state or prior authorization is required. Given no annotations and a weak schema, the description is adequate but not fully complete for safe autonomous invocation.

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

Parameters5/5

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

The description compensates entirely for the 0% schema coverage by defining all six parameters clearly: email, document ID, image source with accepted types, 0-based index, and width/height in points. It also notes which parameters are optional, providing meaning the input schema lacks entirely.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb and resource: 'Inserts an image into a Google Doc from Drive or a URL.' It is specific about the action and the accepted source types. It does not explicitly contrast with the sibling insert_doc_elements, which could also insert images, but the name and scope are focused enough to convey the tool's singular purpose.

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?

No guidance is given about when to use this tool versus alternatives such as insert_doc_elements or batch_update_doc. The description states only what the tool does, not when it should be preferred, what prerequisites exist, or what scenarios are not appropriate.

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