Skip to main content
Glama
OrbiAds

OrbiAds

Official
by OrbiAds
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

creatives

Manage Google Ad Manager creatives and native styles: list, update, archive, preview, and associate with line items via LICAs.

Instructions

Manage GAM Creative entities and native styles — full lifecycle from list to archive, plus LICA management.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5 credits. Bulk operations = 0.5 credits flat. OUTPUT: Returns Creative objects with id, name, type, size, previewUrl, and associated assetIds. Preview URLs expire after 24h. WHEN TO USE: Use creatives for Creative entity management (metadata, associations, lifecycle). Use creative_assets for raw asset file uploads. Use creative_qa for compliance validation. NOTE: A Creative entity in GAM wraps one or more creative_assets. A LICA (LineItem-Creative Association) links a Creative to a LineItem for serving.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • list_creatives_by_advertiser: List all creatives for a given advertiser ID. Read-only. • list_creatives_by_line_item: List all creatives associated with a line item. Read-only. • list_creatives_by_network: List all creatives on the network with optional filters. Read-only. • get_creative: Get a single creative by ID. Read-only. • update_creative: Update a creative's name, size, or snippet. Write. • archive_creative: Archive a creative. Destructive write — removes from active serving. Run pre_archive_check first. • duplicate_creative: Duplicate an existing creative to use as a starting point. Write. • get_creative_preview_url: Generate a preview URL for a creative. Read-only. URL expires after 24h. • get_native_style_preview_urls: Generate preview URLs for a native style across all sizes. Read-only. • get_campaign_preview_links: Get all preview links for a campaign (all creatives + all placements). Read-only. • get_video_transcode_status: Check transcode status for a video creative. Read-only. • list_native_styles: List all native ad styles. Read-only. • get_native_style: Get a specific native style by ID. Read-only. • update_native_style: Update a native style's template or CSS. Write. • archive_native_style: Archive a native style. Destructive write. • duplicate_native_style: Duplicate a native style. Write. • ensure_classic_native_template: Ensure a classic native template exists, creating it if absent. Idempotent write. • list_creative_templates: List all creative templates available on the network. Read-only. • get_creative_template: Get a specific creative template by ID. Read-only. • discover_native_formats: Discover available native ad formats and their required fields. Read-only. • associate_creative: Create a LICA between one creative and one line item. Write. • bulk_associate_creatives: Create multiple LICAs in one call. Write. • get_licas_by_line_item: List all LICAs for a line item. Read-only. • get_licas_batch: Retrieve multiple LICAs by ID. Read-only. • deactivate_lica: Deactivate a LICA without deleting it. Write. • update_lica: Update a LICA's weight or start/end date. Write. • delete_licas: Delete LICAs permanently. Destructive write.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses the mode (mixed read+write), auth requirement (OAuth 2.0), credit costs (reads=0, writes=0.5), output structure (Creative objects with specific fields), and preview URL expiry. Destructive actions like archive include a warning to run pre_archive_check first.

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 labeled sections (MODE, AUTH, CREDITS, OUTPUT, WHEN TO USE, NOTE) and front-loads the main purpose. However, it is slightly verbose in listing action enum options, which are already detailed in the schema, making it somewhat 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?

Given the tool's complexity (multiple actions, LICA management, native styles), the description covers all essential aspects: purpose, usage guidelines, behavioral traits, parameter meanings, and output format. No output schema exists, but the description explains return fields, making it complete for appropriate tool invocation.

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 beyond the schema by including contextual notes (e.g., 'Run pre_archive_check first' for archive actions) and explaining the relationship between Creative entities and LICAs. While the schema's enum descriptions are comprehensive, the description provides additional context for parameter usage.

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 manages GAM Creative entities and native styles, covering full lifecycle and LICA management. It uses a specific verb+resource ('Manage GAM Creative entities and native styles') and distinguishes from siblings like creative_assets and 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 in the 'WHEN TO USE' section, directing users to creative_assets for raw file uploads and creative_qa for compliance validation. It also explains the relationship between Creative entities, creative_assets, and LICAs, aiding correct tool selection.

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