Skip to main content
Glama

graph_move_file

Move or rename a OneDrive file or folder by specifying its item ID and either a destination folder, a new name, or both.

Instructions

Move and/or rename a file or folder in OneDrive.

At least one of new_parent_folder_id or new_name must be provided.

Args: item_id: The file or folder ID to move. new_parent_folder_id: Destination folder ID. Empty to keep the current parent. new_name: New name for the item. Empty to keep the current name.

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_move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
new_nameNo
new_parent_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It says what changes but not what happens on name collisions (overwrite vs. fail), whether moving a folder relocates its contents, what permissions are required, or whether the operation is reversible — all material for a destructive-ish write.

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?

Front-loaded with purpose and the key constraint, then a compact Args block. The Args formatting is slightly verbose but justified here because the schema has zero parameter descriptions, so 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 three-parameter mutation tool with no annotations and no output schema, the description covers inputs and the precondition adequately. It leaves out return behavior (does it return the updated item?) and failure modes such as name conflicts, which an agent needs before invoking a move.

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 coverage is 0%, and the description compensates well: it explains each parameter and, crucially, the non-obvious empty-string semantics ('Empty to keep the current parent' / 'Empty to keep the current name') that the schema's default values do not convey. It does not clarify whether item_id accepts a path or only an opaque ID.

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

Purpose5/5

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

States a specific verb pair ('move and/or rename') and a concrete resource ('a file or folder in OneDrive'), which inherently separates it from graph_copy_file and graph_delete_file without needing to name them. An agent knows exactly what operation this performs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition — at least one of new_parent_folder_id or new_name must be provided — which is real usage guidance not present in the schema (both are optional with empty-string defaults). It stops short of stating when to prefer this over graph_copy_file or noting that renaming alone is a valid no-move call.

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