Skip to main content
Glama

drive_files_update

Update a Google Drive file's name, MIME type, or upload new content by providing the file ID and optional new values.

Instructions

Update a file's metadata or content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdYesThe file ID to update
fieldsNoFields to return
nameNoNew file name
mimeTypeNoNew MIME type
uploadPathNoLocal file path to upload

Implementation Reference

  • The generic tool handler registered via server.tool() for 'drive_files_update'. When the tool is invoked, it calls executeGws() which builds CLI args and spawns the gws process. This is the actual execution logic for drive_files_update.
    server.tool(
      tool.name,
      tool.description,
      schema,
      async (args) => {
        const result = await executeGws(tool, args as Record<string, unknown>, gwsBinary);
    
        if (result.success) {
          return {
            content: [{ type: "text" as const, text: result.output || "(empty response)" }],
          };
        } else {
          return {
            content: [{ type: "text" as const, text: `Error: ${result.error}` }],
            isError: true,
          };
        }
      },
  • buildZodSchema() generates the Zod validation schema for all tools including drive_files_update. It constructs a schema from tool.params and tool.bodyParams definitions, and adds an optional 'uploadPath' field if supportsUpload is true.
    export function buildZodSchema(tool: ToolDef): Record<string, z.ZodTypeAny> {
      const shape: Record<string, z.ZodTypeAny> = {};
    
      const allParams = [...tool.params, ...(tool.bodyParams || [])];
    
      for (const p of allParams) {
        let field: z.ZodTypeAny;
        switch (p.type) {
          case "number":
            field = z.number().describe(p.description);
            break;
          case "boolean":
            field = z.boolean().describe(p.description);
            break;
          default:
            field = z.string().describe(p.description);
        }
    
        if (!p.required) {
          field = field.optional();
        }
    
        shape[p.name] = field;
      }
    
      // Add optional uploadPath for tools that support file upload
      if (tool.supportsUpload) {
        shape.uploadPath = z.string().describe("Local file path to upload").optional();
      }
    
      return shape;
    }
  • src/index.ts:156-178 (registration)
    All tools from the SERVICE_TOOLS registry (including drive_files_update) are registered as MCP tools in a loop over the tools array. drive_files_update is registered here via server.tool() along with all other tools.
    // Register each tool
    for (const tool of tools) {
      const schema = buildZodSchema(tool);
    
      server.tool(
        tool.name,
        tool.description,
        schema,
        async (args) => {
          const result = await executeGws(tool, args as Record<string, unknown>, gwsBinary);
    
          if (result.success) {
            return {
              content: [{ type: "text" as const, text: result.output || "(empty response)" }],
            };
          } else {
            return {
              content: [{ type: "text" as const, text: `Error: ${result.error}` }],
              isError: true,
            };
          }
        },
      );
  • The ToolDef definition for 'drive_files_update' — defines the tool name, description, command (['drive','files','update']), params (fileId required, fields optional), bodyParams (name, mimeType optional), and supportsUpload: true. This is the schema/configuration for the tool.
    {
      name: "drive_files_update",
      description: "Update a file's metadata or content.",
      command: ["drive", "files", "update"],
      params: [
        { name: "fileId", description: "The file ID to update", type: "string", required: true },
        { name: "fields", description: "Fields to return", type: "string", required: false },
      ],
      bodyParams: [
        { name: "name", description: "New file name", type: "string", required: false },
        { name: "mimeType", description: "New MIME type", type: "string", required: false },
      ],
      supportsUpload: true,
      defaultParams: DRIVE_SHARED_DEFAULTS_NO_INCLUDE,
    },
  • executeGws() is the generic helper that executes gws CLI commands. It's called when drive_files_update is invoked. buildArgs() (line 76-129) constructs the CLI arguments including --params, --json, and --upload flags based on the tool definition and user-provided args.
    export async function executeGws(
      tool: ToolDef,
      args: Record<string, unknown>,
      gwsBinary: string,
    ): Promise<ExecResult> {
      const cliArgs = buildArgs(tool, args);
    
      console.error(`[gws-mcp] Executing: ${gwsBinary} ${cliArgs.join(" ")}`);
    
      try {
        const { stdout, stderr } = await spawnGwsRaw(gwsBinary, cliArgs);
    
        if (stderr) {
          console.error(`[gws-mcp] stderr: ${stderr}`);
        }
    
        return { success: true, output: stdout || "(empty response)" };
      } catch (err: unknown) {
        const error = err as { message?: string };
        let message = error.message || "Unknown error";
    
        // Enhance Drive 404 errors with actionable hints
        if (message.includes("404") && message.includes("not found") && tool.command[0] === "drive") {
          message += "\n\nHint: If this file is in a shared drive, ensure supportsAllDrives is set (this should be automatic). Check that the file ID is correct and the authenticated account has access.";
        }
    
        console.error(`[gws-mcp] Error: ${message}`);
        return { success: false, output: "", error: message };
      }
    }
Behavior2/5

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

No annotations provided; description only says 'update' without elaborating on permissions, reversibility, or effects of changing MIME type or uploading content. Lacks behavioral depth.

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?

Single sentence, no filler. Efficiently communicates the core action.

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?

No output schema and no description of return values. Does not clarify if updates are partial or full. Incomplete for a tool with 5 parameters.

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 coverage is 100% with clear parameter descriptions. The description adds no additional meaning beyond the schema, earning the baseline score.

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 verb 'Update' and the resource 'a file', and distinguishes from sibling tools like create, delete, or download. It specifies metadata or content, aligning with the parameters.

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 guidance on when to use this tool vs. alternatives like drive_files_create or docs_batchUpdate. No context on prerequisites 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/conorbronsdon/gws-mcp-server'

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