Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_copy

Duplicate a Google Drive file, such as a template doc, sheet, or deck, with an optional new name and destination folder.

Instructions

Make a copy of a file (e.g. duplicate a template doc/sheet/deck).

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": {
      "fileId": "<fileId>"
    },
    "name": "drive_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
fileIdYes
folderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. However, the description is silent on the behaviors that actually matter for a copy operation: whether the copy lands in the source folder by default, whether sharing permissions and comments are duplicated, and whether the copied file inherits the original's metadata.

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 compact sentence with the operation front-loaded and no filler. It is efficiently sized, though the terseness leaves the surrounding gaps unaddressed rather than intentionally distilled.

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?

For a three-parameter mutation with no output schema and no parameter documentation, the description does not say where the copy is placed, what it is named by default, or what identifier the caller receives. Given the low complexity this is not catastrophic, but the definition leaves more to inference than it should.

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 carries the full burden, yet it explains only the fileId role implicitly. The optional 'name' and 'folderId' parameters — the difference between copying alongside the original versus copying into a target folder with a new name — are never addressed in the description or the schema.

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: 'make a copy of a file', with concrete examples (template doc/sheet/deck) that tell an agent this is a duplication operation rather than a create-from-scratch or move. It does not explicitly contrast itself with siblings such as drive_create_folder or drive_upload_file, but the purpose is unambiguous on its own.

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 template-duplication example implies a usage context (cloning an existing file rather than authoring a new one), but there is no explicit when-to-use vs when-not guidance, no prerequisites, and no mention of alternatives. The agent must infer the selection criteria.

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