Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft image assets

draft_image_assets

Draft campaign image assets from local files, public URLs, or uploads; return a preview plan_id to confirm before applying to Google Ads.

Instructions

Draft campaign image assets from local files, public image URLs or uploads — returns a PREVIEW.

At least one image in total is required across image_paths, image_urls and upload_ids. Images must be PNG, JPEG or GIF and at most 5120 KB (Google's limit). URL images are downloaded now and checked; applying re-downloads them and refuses if the image changed since the preview. Returns a preview with a plan_id and a per-image summary; nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlsNoPublic http(s) URLs of PNG/JPEG/GIF images. Links to private, local or internal addresses are refused.
upload_idsNoIds of images the user uploaded (up_..., from upload_images or list_uploads). The way to use an image that has no public URL.
campaign_idYesNumeric ID of the campaign to attach the images to.
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
image_pathsNoLocal PNG/JPEG/GIF file paths on the machine running AdLoop. Not available on a hosted server, where image_urls applies instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.27.1
    • addedInput schema / properties / campaign_id / description
      Added value: +"Numeric ID of the campaign to attach the images to."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / image_paths / default
      Added value: +[]
    • addedInput schema / properties / image_paths / description
      Added value: +"Local PNG/JPEG/GIF file paths on the machine running\nAdLoop. Not available on a hosted server, where image_urls\napplies instead."
    • addedInput schema / properties / image_urls
      Added value: +{
+  "default": [],
+  "description": "Public http(s) URLs of PNG/JPEG/GIF images. Links to\nprivate, local or internal addresses are refused.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / upload_ids
      Added value: +{
+  "default": [],
+  "description": "Ids of images the user uploaded (up_..., from\nupload_images or list_uploads). The way to use an image that has\nno public URL.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaign_id",
-  "image_paths"
-]New value: +[
+  "campaign_id"
+]
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. First observedv0.9.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses real behavioral traits: nothing mutates until confirm_and_apply runs, the return is a preview with plan_id and a per-image summary, URL images are fetched and validated at draft time, and apply re-downloads and refuses if the image drifted. It also states format and 5120 KB size limits, none of which annotations 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?

The first sentence front-loads purpose and the preview guarantee, and the constraint sentences are compact. The trailing Google Ads API documentation link and line-broken constraint bullets add mild bulk without new information, but nothing is redundant.

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 detail return fields, yet it still names the preview payload (plan_id, per-image summary). Combined with source selection, validation rules, and the apply handoff, an agent has everything needed to invoke 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 the schema already documents each parameter, making 3 the baseline. The description adds value beyond that with the cross-parameter constraint (at least one image across the three source fields) and the explicit 5120 KB ceiling, which the schema does not state.

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 description states a specific verb and resource ('Draft campaign image assets'), enumerates the three input sources, and makes the preview-only nature explicit. It clearly separates itself from siblings such as upload_images (which supplies upload_ids) and confirm_and_apply (which performs the mutation).

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?

It gives a concrete precondition ('At least one image in total is required across image_paths, image_urls and upload_ids') and routes the agent on source choice (upload_ids for images with no public URL; image_paths unavailable on a hosted server). It implies the draft-then-apply flow via confirm_and_apply but never states explicit when-not-to-use conditions.

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

Deploy Server

Other Tools