Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_copy

Creates a copy of a Google Drive file, optionally converting it to another format such as Markdown to Google Doc.

Instructions

Copy a file. Useful for converting formats (e.g. markdown to Google 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": {
      "fileId": "<fileId>",
      "name": "<name>"
    },
    "name": "drive_files_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the copy
fieldsNoFields to return
fileIdYesSource file ID to copy
parentsNoParent folder IDs (JSON array as string)
mimeTypeNoTarget MIME type for conversion

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description's one real contribution is that the copy operation can serve as a conversion mechanism, which is non-obvious. It omits collisions on existing names, whether permissions and parents carry over to the copy, and whether the source is left untouched.

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?

Two short sentences with the core action front-loaded and no filler; the example is compact rather than verbose. It is perhaps slightly too terse for a five-parameter tool, but nothing is wasted.

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 mutating five-parameter tool with no output schema, the description should mention what comes back (a File resource whose shape is controlled by the fields parameter) and the permission/parent inheritance behavior. Those gaps are meaningful, though the annotation set covers the mutation and openness profile.

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?

Schema coverage is 100%, so the schema already documents all five parameters and the baseline is 3. The description adds meaning to mimeType by giving a concrete conversion example (markdown to Google Doc), but says nothing about names, parents, or the fields projection parameter.

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?

A specific verb and resource ("Copy a file") plus a concrete motivating use case, which lets an agent distinguish it from drive_files_create and drive_files_update. It stops short of differentiating from drive_files_export, which is the sibling most likely to be confused with the stated format-conversion use case.

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 it (format conversion, e.g. markdown to Google Doc), which is genuine but partial guidance. It never says when NOT to use it, nor names drive_files_export or download as the alternative for read-only format conversion, even though export is the obvious overlapping sibling.

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