Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_get_file

Read-only

Retrieve metadata for a Google Drive file by file ID or URL to identify its details before sharing, organizing, or processing it.

Instructions

Get metadata for a Drive file (ID or URL).

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

NameRequiredDescriptionDefault
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/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 safety profile is covered. The description adds that only metadata is returned (not file contents), which is useful, but says nothing about permissions, error cases, or what metadata fields are included.

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?

A single short sentence with the resource and the acceptable identifier formats front-loaded. No wasted words.

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?

For a one-parameter read tool with no output schema, this is close to sufficient: it states the resource, the read-only nature is annotated, and the ID/URL flexibility is disclosed. What is missing is any indication of the returned metadata fields or behavior on invalid IDs, which the description could not otherwise be inferred.

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 must carry the parameter burden. It does add real meaning by noting the file identifier may be an ID or a URL, which the bare 'fileId: string' schema does not convey, but it stops there.

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 names a specific verb ('Get metadata') and resource ('a Drive file'), which clearly separates it from content-reading siblings such as drive_read_file_text and drive_download_file. It does not explicitly name those siblings, so differentiation is implied rather than stated.

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 when-to-use or when-not-to-use guidance and no alternative named. An agent must infer from the phrase 'metadata' alone that this is for properties rather than file contents, which is the key routing decision among the drive_* siblings.

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