AdsAgent — Google Ads MCP

creatives_list_cloud

Read-only

List files from the Google Drive cloud-library index. This is not creatives_list_folders and not the upload library. Optional parent_id is a Drive folder id copied from an earlier item's parent_id; it is not an upload-library folder id and not a Drive URL. Empty Drive folders are absent because only files are indexed. Each item includes modified_time (Drive modified time, timezone-aware ISO-8601, or null) and indexed_at. There is no month parameter: compare modified_time yourself. A null modified_time cannot be placed in a calendar month. indexed_at is when the index saw the file, not the file's month. An item may include error_code cloud_file_too_large or cloud_file_type_unsupported; do not use that file in an ad. Supported types: image/gif, image/jpeg, image/png, image/webp, video/mp4, video/quicktime, video/webm. Maximum file size is 524288000 bytes (500 MiB). A larger file returns error_code cloud_file_too_large. Any other type returns error_code cloud_file_type_unsupported. Google Ads images are limited to 5242880 bytes (5 MiB). No writes.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No
`limit`	No
`parent_id`	No	Drive folder id copied from an earlier item parent_id.
`connection_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedInput schema / properties / parent_id

Added value: +{
+  "description": "Drive folder id copied from an earlier item parent_id.",
+  "maxLength": 200,
+  "type": "string"
+}

AddedOct 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses non-obvious behavior: empty folders are absent, no month parameter exists, null modified_time can't be month-bucketed, indexed_at is ingestion time not file month, and which error_codes block ad use. This is exactly the context annotations cannot carry.

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?

Long but dense—nearly every sentence carries a constraint (size limits, type list, error semantics). Front-loaded with the core purpose, though the size/type enumeration 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?

No output schema exists, so the description carries return-value burden and does: it names the returned fields (modified_time, indexed_at, error_code) and their semantics. Combined with the constraints, an agent has enough to call and interpret results.

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 coverage is only 25% (only parent_id documented in-schema), and the description richly explains parent_id (not a URL, not an upload-library id) plus the deliberate absence of a month filter. However, q and limit remain unexplained in both schema and description, leaving gaps for two of four params.

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?

States a specific verb+resource ('List files from the Google Drive cloud-library index') and explicitly distinguishes itself from creatives_list_folders and the upload library. An agent can identify the tool 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?

Explicitly negates two alternatives (creatives_list_folders, upload library) and clarifies parent_id's provenance and what it is not. Lacks a positive 'use this when...' framing, but the negative routing is strong enough to steer selection.

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

All AdsAgent — Google Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?