Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

update_drive_file

Update metadata and properties of a Google Drive file including name, description, parents, star status, trash state, sharing settings, and custom properties. Preview changes with dry run before applying.

Instructions

Updates metadata and properties of a Google Drive file.

Args: user_google_email (str): The user's Google email address. Required. file_id (str): The ID of the file to update. Required. name (Optional[str]): New name for the file. description (Optional[str]): New description for the file. mime_type (Optional[str]): New MIME type (note: changing type may require content upload). add_parents (Optional[str]): Comma-separated folder IDs to add as parents. remove_parents (Optional[str]): Comma-separated folder IDs to remove from parents. starred (Optional[bool]): Whether to star/unstar the file. trashed (Optional[bool]): Whether to move file to/from trash. writers_can_share (Optional[bool]): Whether editors can share the file. copy_requires_writer_permission (Optional[bool]): Whether copying requires writer permission. properties (Optional[dict]): Custom key-value properties for the file. dry_run (bool): If True, returns a preview and does not update the file. Defaults to True.

Returns: str: Confirmation message with details of the updates applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
file_idYes
nameNo
descriptionNo
mime_typeNo
add_parentsNo
remove_parentsNo
starredNo
trashedNo
writers_can_shareNo
copy_requires_writer_permissionNo
propertiesNo
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description partially discloses behavior: dry_run defaults to True (preview mode), and changing MIME type may require content upload. However, it omits permission requirements, rate limits, or whether updates are reversible.

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?

The description is verbose but well-structured with Args and Returns sections. It is front-loaded with the purpose. Every sentence adds value, though slight redundancy in the parameter list could be trimmed.

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?

Given 13 parameters and no annotations, the description covers inputs and return value adequately. It includes the dry_run behavior and a warning on MIME type changes, but lacks examples, error handling, or authentication prerequisites.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully documents each parameter with types, optionality, and contextual notes (e.g., mime_type note, dry_run default). This adds significant meaning beyond the schema.

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 'Updates metadata and properties of a Google Drive file,' specifying the action and resource. It distinguishes from sibling tools that focus on content (update_google_doc) or permissions (update_drive_permission).

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?

No explicit guidance on when to use this tool versus alternatives like update_google_doc or update_drive_permission. The description does not provide context or exclusions.

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/Skeptomenos/google-workspace-mcp-advanced'

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