Browse documentation
On this page
Upload Meta images and hand them to an ad batch
Upload actual image files with approval, retain returned hashes, and recover from partial uploads without duplicates.
Try this in your assistant
Upload these attached images to Meta account [name or ID] in workspace [name]. Preview the filenames, account and fingerprints for my approval. After upload, report the returned image hashes. Do not create or activate ads.
Use the actual files
Pass the attached or generated image files through the assistant’s supported file handoff. Use the single-image tool for one file and the batch upload tool for multiple files; the batch accepts up to ten files per call.
The file parameter can be adapted by the host. Follow the schema exposed in the connected assistant rather than putting local paths into a download URL field. If native handoff fails or files are unavailable, use the image-picker fallback.
Approve the upload preview
The preview identifies the intended account, files and SHA-256 fingerprints. After approval, submit the matching fingerprints with the same files and account. A changed file needs a fresh preview.
A successful upload returns a Meta imageHash. Retain it for ad creation. Upload approval does not authorize creating ads or enabling delivery.
Handle partial results and continue safely
Report successful files and failed files separately. Reuse successful image hashes instead of re-uploading them. After an ambiguous timeout, inspect the account before repeating a write.
When moving to a saved Meta ad batch, review its full mapping and obtain approval separately. Use get_meta_ads_batch to inspect queued, running, waiting and completed work; an uncertain result is not a reason to recreate the batch.
Tool reference
Selected tools used in this guide. Names, descriptions and declared input fields are extracted from the MCP implementation. The connected assistant exposes the complete live schema, including field types, limits and account-routing options.
Upload a ChatGPT image to Meta Adsupload_meta_image_file
Default tool for requests like 'upload this image to Meta', 'upload the images you generated', or 'upload these 10 creatives to Account 3'. Use the actual attached/generated PNG or JPEG, up to 3 MB. When the host exposes file as a string described as an absolute local file path, pass the existing absolute path directly in file; the host supplies the downloadable file. Do not mistake file:string for unsupported handoff, fabricate URLs, or put a path inside download_url. Prefer this tool over the picker and base64. For multiple images prefer upload_meta_image_files to avoid repeated calls. Use individual previews and uploads only if the host cannot provide batch file inputs. Reuse the resolved workspace/account and never ask the user for tool names or URLs. Return and retain each Meta imageHash; do not repeat successful uploads. Uploads do not create or activate ads.
Declared input fields
workspaceIdfileconfirmedapprovedSha256
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
Upload multiple ChatGPT images to Meta Adsupload_meta_image_files
Preferred for 'upload these images', 'upload all 10 creatives', or other multi-image uploads. Accepts 1–10 actual files through native file handoff. If the host exposes files as paths, pass the existing absolute image paths directly. Preview the whole batch with confirmed=false, present one batch approval, then use confirmed=true and approvedSha256s in exactly the same file order. Two files are processed concurrently. Retain every successful imageHash, report failed/unknown items separately, and never retry the whole batch after partial success. Does not create or activate ads.
Declared input fields
workspaceIdfilesconfirmedapprovedSha256s
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
Read Meta batch execution resultsget_meta_ads_batch
Read saved per-item stages, creative IDs and ad IDs. Queued/running/waiting plans are executed by PlugMind in the background. Waiting includes available_at for the next attempt. Completed IDs are retained. Never recreate completed or uncertain items.
Declared input fields
workspaceIdplanId
Use the current assistant schema for required fields, defaults and nested structures. This reference is not an executable request.
Put it into practice
Meta bulk image-ad creation
Turn uploaded images and approved copy into a tracked batch of paused Meta ads in existing ad sets.
ExploreRelated documentation
Meta batch execution and recovery
Understand approved Meta ad batches, waiting states, partial success and recovery without duplicate ads.
ExploreMeta permissions and asset access
Diagnose missing Meta permissions, Page access and ad identities before creating Facebook or Instagram ads.
ExploreSelect the right workspace and advertising account
Resolve client workspaces and account IDs before reporting or making approved changes.
Explore