Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_delete_range

Destructive

Deletes content between specified start and end indices in a Google Doc, using index values from structured document reads to remove targeted text or sections.

Instructions

Delete content between two indices (get indices from docs_read structured).

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>",
      "startIndex": "<startIndex>",
      "endIndex": "<endIndex>"
    },
    "name": "docs_delete_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
endIndexYes
documentIdYes
startIndexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known from structured data. The description adds nothing beyond that: no statement about irreversibility, undo availability, atomicity, or how surrounding document structure is affected (e.g., whether adjacent elements merge).

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?

One short sentence, front-loaded with the action and resource, with the parenthetical pointing to index sourcing. Nothing is padded, though the terseness leaves the parameter gaps noted above unfilled.

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?

For a three-parameter destructive tool with no annotations beyond the risk hints and no output schema, the definition covers what to do and where the inputs come from. It is missing reversibility and index-range boundary semantics that an agent would need to invoke it safely and correctly, so it is adequate rather than complete.

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

Parameters3/5

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

With 0% schema description coverage, the description carries the full burden, and it partially meets it by explaining that startIndex/endIndex are indices and where to source them. It omits critical semantics such as whether the range is inclusive or exclusive, what units indices are in (UTF-16 code units vs. characters), and whether startIndex must be less than endIndex. documentId is 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?

The description states a specific verb and resource ('Delete content between two indices'), which is unambiguous and tells an agent this is a range-based deletion rather than a replacement or insertion. It does not explicitly contrast itself with siblings such as docs_replace_text or docs_batch_update, so it stops short of full sibling differentiation.

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?

It gives one concrete usage prerequisite — obtain indices from docs_read structured — which is genuinely actionable. It offers no when/when-not guidance, such as preferring docs_replace_text when swapping text rather than deleting and re-inserting, so usage is only implied.

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