Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads list image assets

google_ads_list_image_assets

Read-onlyIdempotent

Lists an account's image asset library with full-size URLs, dimensions, file size, and MIME type. Returns newest first and supports filtering by dimensions, file name, or asset IDs.

Instructions

List the account's image asset library (FROM asset) with stable, publicly served full-size URLs on tpc.googlesyndication.com, dimensions, file size, and mime type. This is the whole stock and carries no notion of delivery: an asset uploaded in 2022 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. Shopping product imagery lives in Merchant Center, not in this library.

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.
`minWidth`	No	Only images at least this wide, in pixels
`minHeight`	No	Only images at least this tall, in pixels
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`nameFilter`	No	Only assets whose file 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.

Changed7 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"
```
addedInput schema / properties / minHeight / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / minWidth / maximum
```
Added value: +9007199254740991
```

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

A4.8/5.0

Behavior5/5

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

Goes well past readOnly/idempotent annotations: it discloses that URLs are stable and publicly served on tpc.googlesyndication.com, that the library has no notion of delivery (2022-uploaded assets look identical to running ones), that ordering is newest-first, and that the response count is the account total rather than the page size.

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?

Dense and front-loaded: the resource, the returned fields, and the key caveat about no delivery data come first. A few clauses (local-server note, Shopping comparison) are slightly tangential but still aid disambiguation.

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 an output schema present, the description needn't document return shape, and it still covers ordering, pagination semantics, total-count meaning, and the absence of delivery/performance data — everything needed to call it correctly.

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 100%, so baseline would be 3, but the description adds real meaning: limit returns recent assets rather than an arbitrary slice, and continue-paging via beforeAssetId must reuse the same filters. It does not explicitly explain assetIds or the dimension filters beyond schema text.

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 and resource ('List the account's image asset library (FROM asset)') plus the fields returned (URLs, dimensions, file size, mime type). It is clearly separable from siblings like google_ads_list_video_assets, google_ads_get_pmax_assets, and google_ads_get_shopping_products.

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 routes agents away from this tool when delivery-over-time or visual gallery is needed ('use the hosted GetMCPAds service') and states that Shopping product imagery lives in Merchant Center. It also clarifies the local server's scope, giving when-to-use and when-not-to-use.

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

Deploy Server