Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_insert_image

Insert an image from a public URL directly into a Google Doc at a chosen position and width to add visual content without manual uploads.

Instructions

Insert an image from a public URL into a Doc.

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": {
      "documentId": "<documentId>",
      "imageUrl": "<imageUrl>"
    },
    "name": "docs_insert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo
widthPtNo
imageUrlYes
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the meaningful constraint that the image is fetched from a public URL (explaining the open-world trait), but says nothing about positioning behavior, whether existing content shifts, or what happens on an unreachable/large image.

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?

A single front-loaded sentence with zero filler, and the key constraint (public URL) appears early. Its brevity is clean rather than padded, though it borders on under-specification rather than earning credit for terseness alone.

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?

For a mutating 4-parameter tool with no output schema and no parameter documentation anywhere, one sentence is not enough. Missing are index semantics (and its negative-value behavior), widthPt behavior, and any note on how insertion affects surrounding document content.

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% across 4 parameters, so the description must carry parameter meaning and largely does not. 'imageUrl' and 'documentId' are only obliquely gestured at ('public URL', 'into a Doc'), while 'index' (insertion position) and 'widthPt' (image sizing, and whether aspect ratio is preserved) are never mentioned.

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?

States a specific verb and resource ('Insert an image') plus the target ('into a Doc'), which distinguishes it from docs_insert_markdown and docs_insert_table by content type. It stops short of naming those siblings explicitly, but the resource noun does the differentiation work.

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 when-to-use guidance versus docs_insert_markdown/docs_insert_table/docs_batch_update, and no stated preconditions beyond the implicit 'public URL' requirement in the sentence. An agent must infer that the URL must be reachable without auth and that this tool is single-image only.

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