Skip to main content
Glama

update_drive_file

Update a Google Drive file's name, description, folder parents, trash, star, and sharing flags without uploading new content.

Instructions

Update a Drive file's metadata, folder parents, and flags.

Side effects: mutates the file (rename, move via add/remove_parents, trash/untrash, star). Does NOT upload new content — for content use a native-app tool or create_drive_file. trashed=True is reversible with trashed=False until the file is permanently deleted. Requires the drive.file OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
file_idYesDrive file ID to update.
nameNoNew display name.
descriptionNoNew description text.
mime_typeNoNew MIME type (changing this rarely works without also uploading matching content).
add_parentsNoComma-separated folder IDs to add the file into (effectively moves when combined with remove_parents).
remove_parentsNoComma-separated folder IDs to detach from.
starredNoTrue to star, False to unstar.
trashedNoTrue moves to Trash (soft-delete), False restores.
writers_can_shareNoWhether editors may re-share the file.
copy_requires_writer_permissionNoWhen True, copies require writer access (reader copy/export blocked).
propertiesNoDict of user-visible custom key-value pairs attached to the file.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv1.0.0
    • changedInput schema / properties / add_parents / description
      Previous value: -"Comma-separated folder IDs to add as parents."New value: +"Comma-separated folder IDs to add the file into\n(effectively moves when combined with remove_parents)."
    • changedInput schema / properties / copy_requires_writer_permission / description
      Previous value: -"Whether copying requires writer permission."New value: +"When True, copies require\nwriter access (reader copy/export blocked)."
    • changedInput schema / properties / description / description
      Previous value: -"New description for the file."New value: +"New description text."
    • changedInput schema / properties / file_id / description
      Previous value: -"The ID of the file to update. Required."New value: +"Drive file ID to update."
    • changedInput schema / properties / mime_type / description
      Previous value: -"New MIME type (note: changing type may require content upload)."New value: +"New MIME type (changing this rarely works without\nalso uploading matching content)."
    • changedInput schema / properties / name / description
      Previous value: -"New name for the file."New value: +"New display name."
    • changedInput schema / properties / properties / description
      Previous value: -"Custom key-value properties for the file."New value: +"Dict of user-visible custom key-value pairs attached\nto the file."
    • changedInput schema / properties / remove_parents / description
      Previous value: -"Comma-separated folder IDs to remove from parents."New value: +"Comma-separated folder IDs to detach from."
    • changedInput schema / properties / starred / description
      Previous value: -"Whether to star/unstar the file."New value: +"True to star, False to unstar."
    • changedInput schema / properties / trashed / description
      Previous value: -"Whether to move file to/from trash."New value: +"True moves to Trash (soft-delete), False restores."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
    • changedInput schema / properties / writers_can_share / description
      Previous value: -"Whether editors can share the file."New value: +"Whether editors may re-share the file."
  2. First observedv1.19.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses side effects (rename, move, trash, star) and notes that trashing is reversible. It also warns that changing mime_type rarely works without content. With no annotations provided, the description carries the transparency burden and does so adequately.

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?

The description is concise, with each sentence adding distinct information: purpose, side effects, exclusions, reversibility, and authentication. No redundancy or fluff.

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?

Covers the main aspects of the tool: what it updates, side effects, what it does not do, reversibility, and auth scope. An output schema exists, so return values are handled externally. A minor gap is lack of explanation for add_parents/remove_parents move behavior, but the schema covers that detail.

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 100%, so the description does not need to explain individual parameters. It adds value by grouping parameters into categories (metadata, parents, flags) and adding clarifying notes like the reversibility of trashed, but this does not significantly exceed the schema's information.

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?

The description clearly states the tool updates metadata, folder parents, and flags. It distinguishes itself from content creation tools by explicitly stating it does NOT upload content, and mentions alternatives like create_drive_file.

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?

Provides guidance on when not to use (for content uploads) and mentions the required OAuth scope. It could be more explicit about when to prefer this over other update tools, but the context is clear given the sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server