Google Workspace MCP

drive_get_file

Read-only

Retrieve metadata for a Google Drive file by ID, including name, type, size, owners, sharing settings, and link.

Instructions

Metadata for one file: name, type, size, owners, sharing and link.

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_get_file"
  }
}

Input Schema

Name	Required	Description	Default
`fileId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds useful context by specifying that the result contains metadata fields including sharing and link, but it does not disclose details like permission requirements, response format details, or pagination, if any. This is adequate but not rich.

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 a single, front-loaded sentence that immediately states the operation and resource, then lists the returned metadata fields. There is no filler or redundant restatement of the tool name.

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?

For a simple one-parameter read tool with readOnlyHint and openWorldHint annotations, the description covers the key return fields and makes the tool's purpose understandable. There is no output schema, so the listed metadata fields partially substitute for it, though more detail on the response structure could make it fully complete.

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?

The schema has 0% description coverage, so the description carries the burden of explaining parameters, but it does not mention fileId at all. The connection between 'one file' and the required fileId is inferable, and the parameter name is self-explanatory, yet the description adds little beyond the schema.

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 clearly states the verb 'get' and the resource 'one file', and specifies the return content as metadata fields such as name, type, size, owners, sharing and link. This distinguishes it from siblings like drive_export, which deals with file content, and drive_search, which lists files. It could be stronger by naming the siblings explicitly, but the differentiation is clear enough.

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 guidance on when to use this tool versus alternatives such as drive_search or drive_export. The description implies retrieving metadata for a known file, but it does not state exclusions, prerequisites, or the condition that would make a sibling tool more appropriate.

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