Skip to main content
Glama
OrbiAds

OrbiAds

Official

creative_assets

Upload and create creative assets for Google Ad Manager. Supports image, HTML5, video, audio, companion, and third-party files. Includes bulk upload, compression, and validation actions.

Instructions

Upload and create GAM creative asset files — images, HTML5, video, audio, and companion ads.

MODE: write (all actions upload or create assets) AUTH: OAuth 2.0 required CREDITS: 0.5 credits per upload/create action. OUTPUT: Returns CreativeAsset objects with assetId, fileName, fileSize, mimeType, and a preview URL. SIDE EFFECTS: Assets are stored in GAM and consume storage quota. compress_image modifies the asset file in-place. WHEN TO USE: Use creative_assets for asset file management (uploading raw files). Use creatives for full Creative entity management (associate assets with creative templates). Use creative_qa to validate assets after upload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • bulk_upload: Upload multiple asset files in one call. Returns list of assetId per file. Preferred over individual uploads for batch workflows. • upload_from_url: Download a file from a URL and upload it to GAM as an asset. Write. Requires source_url and file_name. • upload_and_associate: Upload an asset and immediately associate it with an existing creative. Write. • upload_html5_zip: Upload an HTML5 ZIP package and validate its structure before storage. Returns assetId and a list of validation warnings. • create_image: Create an image asset from raw bytes or a local file path. Write. • create_html5: Create an HTML5 asset from inline HTML/CSS/JS content. Write. • create_html5_from_files: Create an HTML5 asset by bundling multiple local files. Write. • create_video: Create a video creative asset (VAST URL or inline video). Write. • create_audio: Create an audio creative asset. Write. • create_vast_redirect: Create a VAST redirect creative that points to an external VAST URL. Write. • create_companion: Create a companion ad asset associated with a video creative. Write. • create_third_party: Create a third-party tag creative asset (JavaScript or iframe snippet). Write. • create_classic_native: Create a classic native ad asset with headline, body, image, and CTA fields. Write. • compress_image: Compress an existing image asset to reduce file size. Modifies asset in-place. Write. • get_video_transcode_status: Check the status of a video transcode job. Read-only. Returns status: PENDING | PROCESSING | COMPLETE | FAILED.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
Behavior4/5

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

With no annotations, the description discloses MODE (write, though one read-only sub-action exists), AUTH (OAuth 2.0), CREDITS (0.5 per action), OUTPUT (CreativeAsset objects with fields), and SIDE EFFECTS (storage quota, in-place compression). It does not cover rate limits or error handling, but overall is transparent.

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 description is well-structured with clear sections and detailed action lists. While somewhat lengthy, the complexity of 15 sub-actions justifies the length. It is front-loaded with the main purpose and structured for easy scanning.

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?

No output schema exists, so the description compensates by specifying return fields (assetId, fileName, etc.). It also covers auth, credits, and side effects. For a tool with many sub-actions and no output schema, it is reasonably complete.

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 is 3. The description adds value by detailing each action sub-operation with syntax and behavior beyond the schema's enum definition. The network_code parameter also has a clear description. This exceeds the baseline.

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 clearly states the tool's purpose: 'Upload and create GAM creative asset files — images, HTML5, video, audio, and companion ads.' It also differentiates from sibling tools (creative_assets vs. creatives vs. creative_qa) in the WHEN TO USE section.

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?

The description explicitly provides WHEN TO USE guidance, distinguishing between creative_assets for file management, creatives for creative entity management, and creative_qa for validation. It also includes MODE, AUTH, CREDITS, OUTPUT, and SIDE EFFECTS sections, offering comprehensive context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrbiAds/Orbiads-GAM-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server