Skip to main content
Glama

Drive folder

drive_folder
Read-onlyIdempotent

Reads the creatives in a Google Drive folder shared with the workspace's Google address. With folderId (the folder_id of a drive_folder mention, or one a search returned) it lists every image and video down to three levels, each with its path, the ratio Drive measured (9:16, 4:5, 1:1, 1.91:1), pixel size, video duration and file size, then Adrails' default grouping into ads: each file at the top of the folder is one ad, and each subfolder is one ad whose files are the same creative in several ratios. Without folderId it returns the folders whose name contains query. The listing keeps the durations, ratios and names that show when files are organized another way, such as ratio names in file names or raw and logo files. An empty result means no folder shared with the workspace's Google address matches. Read only.

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": {
      "input": "<input>"
    },
    "name": "drive_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description does add real behavior beyond that: three-level recursion depth, the exact fields returned per file, the default ad-grouping rule, and that an empty result means no shared folder matched. However, the closing 'Read only.' merely repeats the annotation, and pagination or volume limits are unaddressed.

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?

The main behavior is front-loaded in the first sentence, and the mode split follows immediately, which is good ordering. It is a dense single paragraph, and the sentence about listings preserving durations and ratios for files organized another way is hard to parse and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description fully covers the return shape: per-file path, measured ratio, pixel size, video duration, file size, plus the default ad grouping and the meaning of an empty result. For a read-only, four-parameter nested-schema tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, with query and folderId carrying no schema descriptions; the prose compensates by explaining that folderId is the folder_id from a drive_folder mention or a prior search, and that query matches folders whose name contains it. adPerFile's effect is left to its schema description, so not every parameter is amplified.

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 opening sentence states a specific verb and resource (reads creatives in a shared Google Drive folder), and the description immediately delineates two distinct operating modes: folder listing with folderId and folder search by name without it. No sibling tool covers Drive folder traversal, so an agent can route here without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is made explicit through the parameter-driven split: supply folderId to enumerate creatives, omit it to search folders by query. That is clear conditional guidance, but it never names an alternative tool (e.g. campaign_media or creative_review) or states when-not to use this one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.