Skip to main content
Glama

drive rename file

drive_rename_file
Idempotent

Rename a Google Drive file by specifying its file ID and the new name. Update file titles directly without downloading or re-uploading the file.

Instructions

Rename a Drive file.

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>",
      "new_name": "<new_name>"
    },
    "name": "drive_rename_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
new_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — it does not say whether the file ID or links survive a rename, whether name collisions are rejected or auto-suffixed, or what permissions are required.

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 front-loaded sentence with zero filler, so nothing is wasted. But the terseness crosses into under-specification rather than efficient communication.

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, and annotations cover the safety profile. Still, for a two-parameter mutation tool with zero schema description coverage, the description is too thin to let an agent invoke it confidently.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — both required parameters appear only as titles ('File Id', 'New Name'). The description does not compensate by explaining ID format, whether an extension must be included in new_name, or how duplicate names are handled.

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 description gives a verb and resource ("Rename a Drive file"), which is enough to tell it apart from copy/delete/trash siblings at a glance. However, it is essentially a prose restatement of the tool name 'drive_rename_file' and adds no specificity about what a rename entails.

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 (e.g. write access or ownership), and no mention of how this differs from siblings such as drive_move_file. The agent must infer that renaming is distinct from moving purely from the verb.

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