Skip to main content
Glama

Coline

Copy a file

copy_drive_file

Makes a copy of a file or a whole folder in a drive and folder the person can add to.

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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>",
      "destinationDriveId": "<destinationDriveId>"
    },
    "name": "copy_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
fileIdYesFile or folder id from list_drive_files, search or fetch.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
destinationDriveIdYesDrive id from list_drives.
destinationParentIdNo

Output Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is partially covered. The description adds that whole folders can be copied, but omits important behavior: whether folder copies are recursive, what happens to permissions/inheritance, how name collisions are handled, and what the destination defaults to when destinationParentId is null.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no padding, which is good, but the phrasing "in a drive and folder the person can add to" is awkward and buries the destination concept rather than front-loading it.

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?

An output schema exists, so return values need not be explained, but this is a 5-parameter mutation tool with three required IDs and an undefined naming behavior. The description leaves destination semantics, folder-copy semantics, and collision handling entirely unaddressed, which is insufficient for the tool's complexity.

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 60%, so the baseline is low-3 territory. The description only obliquely gestures at destinations ("a drive and folder") and says nothing about the optional name parameter, which has no schema description at all, nor about root-level placement when destinationParentId is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb and resource are present ("Makes a copy of a file or a whole folder"), which goes beyond the bare title, and it correctly signals that folders are copyable. However, the trailing phrase "in a drive and folder the person can add to" is vague about the destination and does not distinguish this from the sibling copy_shared_file or clarify when each applies.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as copy_shared_file or restore_drive_file. The agent must infer the choice from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources