Skip to main content
Glama
Sign In
drive-mcp

drive-mcp

by reisbel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_file_metadata

Retrieve full metadata for a Google Drive file by its ID, including folder path and web link, to locate or reference files without browsing.

Instructions

Full metadata for one file, including its folder path and web 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": "get_file_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It hints at the return contents (folder path, web link) but says nothing about read-only safety, permissions required, or behavior when the fileId is missing or trashed — thin for a tool with zero annotation coverage.

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 front-loaded sentence with no filler, and the payload hint is attached at the end. Appropriately sized, though it is terse to the point of leaving gaps rather than being a model of efficiency.

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, the description must convey the return shape; it does so only partially (folder path, web link) and omits param documentation in a context where the schema also omits it. Minimum viable for a simple one-parameter read, but not 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?

Schema description coverage is 0% and the description never mentions fileId, so the single parameter's format and provenance are undocumented. The name is self-explanatory enough to be usable, but no meaning is added 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?

States a specific verb+resource ('Full metadata for one file') and previews the payload ('folder path and web link'), which distinguishes it from read_file_content and get_file_permissions among the siblings. It stops short of explicitly naming those alternatives, but the read-only intent is unambiguous.

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 call this versus get_file_permissions, read_file_content, or list_folder, nor any stated precondition (e.g., a valid fileId obtained elsewhere). The agent must infer usage entirely from the name.

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

Deploy Server

Other Tools