Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads list video assets

google_ads_list_video_assets

Read-onlyIdempotent

Lists an account's YouTube video assets, newest first, and returns watch, embed, and thumbnail URLs so you can inspect or display Google Ads video creative.

Instructions

List the account's YouTube video assets (FROM asset) with derived watch, embed, and public thumbnail URLs. This is the whole stock and carries no notion of delivery: an asset uploaded years ago and never served appears exactly like one running today. Newest first, so a limit returns recent assets rather than an arbitrary slice, and the count in the response is the account total. For a visual-only gallery of assets with delivery over dates, use the hosted GetMCPAds service (Performance Max coverage). The local server returns media URLs and native report data. Google Ads exposes no downloadable video file: PMax and Demand Gen videos are hosted on YouTube, so display them via embed or thumbnails.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`assetIds`	No	Resolve these exact native asset IDs, without scanning the library.
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`nameFilter`	No	Only assets whose name contains this text
`beforeAssetId`	No	Continue the descending library before this last-seen asset ID. Use the same filters.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / assetIds / items / $ref
```
Removed value: -"#/properties/beforeAssetId"
```
addedInput schema / properties / assetIds / items / pattern
```
Added value: +"^\\d+$"
```
addedInput schema / properties / assetIds / items / type
```
Added value: +"string"
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds real context beyond that: newest-first ordering, that the response count is the account total, and that no downloadable video file exists (must embed/thumbnail). However it says nothing about pagination behavior or rate/limit constraints despite declaring a 10,000 max.

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?

Purpose and scope are front-loaded in the first sentence, and each subsequent sentence carries a distinct fact (ordering, count semantics, alternative service, no downloadable file). It is slightly longer than needed and the YouTube-hosting sentence sits at the tail where it is least actionable.

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

Completeness4/5

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

With an output schema present, return values needn't be explained, and the description covers ordering, total-count semantics, and the alternative tool. The only meaningful omission is that pagination via beforeAssetId is left entirely to the schema, which is acceptable given the tool's read-only simplicity.

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 100%, so the schema already documents all five parameters, establishing a baseline of 3. The description contributes meaning only for 'limit' by explaining that newest-first ordering makes a limit return recent assets rather than an arbitrary slice; assetIds, nameFilter, and beforeAssetId get no description-level elaboration.

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?

Opens with a specific verb and resource ('List the account's YouTube video assets') plus the derived fields returned (watch, embed, thumbnail URLs), which is far more than the title restates. It distinguishes itself from the hosted gallery service, but never names the closest local siblings (google_ads_list_image_assets, google_ads_get_pmax_assets) as the tools it is not.

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 routes the agent elsewhere when delivery-over-time matters: 'For a visual-only gallery of assets with delivery over dates, use the hosted GetMCPAds service.' It also states the negative condition for this tool ('carries no notion of delivery'). It stops short of contrasting with the sibling asset-listing tools.

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

Deploy Server