Skip to main content
Glama

graph_copy_file

Copies a OneDrive file or folder to a chosen destination folder with an optional new name, using Microsoft Graph’s asynchronous copy operation.

Instructions

Copy a file or folder in OneDrive.

The copy is asynchronous: Graph returns 202 with a monitor URL rather than the finished item, so the new item may not exist yet when this call returns.

Args: item_id: The file or folder ID to copy. destination_folder_id: Destination folder ID. Empty to copy into the current parent. new_name: Name for the copy. Empty to keep the current name. drive_id: Drive ID to act on. Empty targets your own OneDrive.

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": {
      "item_id": "<item_id>"
    },
    "name": "graph_copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
drive_idNo
new_nameNo
destination_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that Graph returns 202 with a monitor URL and that the new item may not exist when the call returns — a critical, non-obvious trait that prevents premature follow-up reads. It omits permission requirements, cross-drive copy constraints, and what happens on name collisions.

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

Conciseness5/5

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

Front-loaded with the action, immediately followed by the async caveat, then a compact Args block. Every sentence adds information an agent needs and there is no filler.

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 4-param mutation tool with no annotations and no output schema, the definition covers the essential async return behavior and all parameters. Gaps are secondary: overwrite/conflict semantics, permission scope, and poll cadence against the monitor URL.

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

Parameters4/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 documents all four parameters with their meaning and default semantics (empty drive_id = own OneDrive, empty destination_folder_id = current parent, empty new_name = keep current name). It does not describe ID format or whether destination_folder_id may reference another drive.

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 file or folder in OneDrive'), which is a distinct operation from sibling graph_move_file or graph_create_folder. It stops short of explicitly contrasting with those siblings, but the verb alone is unambiguous.

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?

Usage is implied rather than stated: the async note tells the agent the copy is not immediately visible, which affects follow-up calls, and default-value hints ('Empty to copy into the current parent') steer invocation. There is no explicit when-to-use-this-vs-move/create guidance and no stated prerequisites or conflict behavior.

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

Deploy Server

Other Tools