Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_update_metadata

Rename a Drive file, edit its description, or star and unstar it by file ID to keep shared content labeled and easy to find.

Instructions

Rename a file, change its description, or star/unstar it.

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": {
      "fileId": "<fileId>"
    },
    "name": "drive_update_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
fileIdYes
starredNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description usefully adds which attributes are mutable, but omits key behavior for a metadata patch: whether unspecified fields are preserved, what happens if fileId is invalid, and whether special characters or length limits apply to name/description.

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?

A single tight sentence with no filler, front-loaded with the most common action. It could have spent the same words clarifying fileId or partial-update behavior rather than enumerating fields the schema already names.

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?

With no output schema and zero schema descriptions, the definition is the only source of parameter meaning and mutation semantics. It covers the editable fields adequately but leaves the required fileId and the question of how omissions are handled unexplained, which is a meaningful gap for a four-parameter write tool.

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 0%, so the description carries the documentation burden; it explains the meaning of name, description and starred, but never mentions fileId, the one required parameter that identifies the target file. Three of four parameters get plain-language meaning, but the required identifier and the partial-update semantics of omitted fields go unaddressed.

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?

The description gives specific verbs (rename, change description, star/unstar) against a specific resource (a file), which maps cleanly onto the drive_update_metadata name. It implicitly separates itself from mutating siblings like drive_update_permission, drive_move and drive_trash by enumerating the metadata fields it touches, though it never names an alternative explicitly.

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 statement of when to use this tool instead of drive_update_permission, drive_move or drive_trash, and no prerequisites such as required write scope or ownership. An agent must infer selection purely from the field list.

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