Skip to main content
Glama

drive copy file

drive_copy_file

Copy a Google Drive file, optionally into another folder, and set a new name for the duplicate.

Instructions

Copy a Drive file, optionally into another folder. Write operation.

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": {
      "file_id": "<file_id>"
    },
    "name": "drive_copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
file_idYes
parent_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

"Write operation" simply restates readOnlyHint=false from the annotations, adding no new information. The description does not disclose what carrying a copy implies, such as whether sharing/permissions are duplicated, how name collisions are handled, or whether the source is left untouched, which is the main behavioral question for a copy tool.

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, front-loaded sentences with no filler or hedging. It is efficient, though the second sentence ("Write operation") is largely redundant with the annotations.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile (non-destructive, non-idempotent, open-world). Still, an agent calling this on a 3-parameter, 0%-coverage schema lacks explanation of the name parameter and of copy-specific behavior like collision handling.

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 description coverage is 0%, so the description must compensate and it only partly does: "Copy a Drive file" maps to file_id and "optionally into another folder" maps to parent_id. The name parameter, which presumably renames the copy, is never mentioned, leaving one of three parameters without semantic explanation.

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 ("Copy a Drive file") plus optional scoping ("into another folder"), which distinguishes it from siblings like drive_move_file or drive_upload_file. It does not explicitly name a sibling it is not, so it falls short of a 5.

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 on when to use copy versus move, upload, or download, and no prerequisites or exclusions. The phrase "optionally into another folder" hints at a use case but is really parameter context rather than usage guidance.

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