Skip to main content
Glama

Adrails

by ai.adrails
OverviewDiscussionsAdmin

Drive folder

drive_folder
Read-onlyIdempotent

Reads the creatives in a Google Drive folder. With folderId (the folder_id of a type=drive_folder mention, or one returned by a search) 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), its pixel size, a video's duration and the file size, then how Adrails would group them into ads by default: each file at the top of the folder is one ad, each subfolder is one ad whose files are the same creative in several ratios. Without folderId it returns folders whose name contains query, most recently changed first. People file creatives their own way: when the default grouping does not fit what you see (the same duration across ratios in different folders, ratio names in file names, raw footage, logos), say how you would group them and ask the one question that decides it. Read only: it uploads and launches nothing. It reaches the folders shared with the workspace's Google address: when nothing matches, the folder is not shared with it yet. Ask open launch questions in this conversation through launch_brief, passing userStatement verbatim. There is no embedded card; show the browser approval link for any proposed advertising change. MCP: use the input object for tool arguments. UI reports and questions are returned as structured content. Free: MCP tool calls use no Adrails credits.

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired 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.
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. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: states it uploads and launches nothing, scopes access to folders shared with the workspace's Google address, explains the empty-result meaning (not shared yet), and notes there is no embedded card and approvals go through the browser link.

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?

Front-loaded with the core read action and the folderId branch before the search fallback. Dense and somewhat run-on, with politeness/UI instructions (browser approval link) that could be trimmed, but nearly every sentence carries behavioral information.

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?

With no output schema, the description fully specifies the return shape (path, measured ratio, pixel size, duration, file size, default ad grouping, three-level depth) plus failure modes and follow-up routing — everything needed to call and interpret it.

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?

Adds real meaning for folderId (provenance: a type=drive_folder mention or a search result) and query (name-contains match, most recently changed first), which the bare schema lacks. adPerFile and accountIds carry their semantics mostly in the schema, so not a full 5.

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?

Specific verb and resource: reads the creatives in a Google Drive folder, and states two distinct modes (list by folderId vs search by query). Clearly distinguishable from siblings like creative_review or campaign_media.

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

Usage Guidelines5/5

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

Explicitly defines when folderId is present vs absent and what each branch does; also instructs what to do when the default grouping doesn't fit (say how you'd group and ask the deciding question) and routes launch questions to launch_brief.

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

All Adrails toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources