Skip to main content
Glama
OrbiAds

OrbiAds

Official

creative_wrapper_skill

Inject scripts around all creatives served on an ad unit or placement to add measurement, viewability, or brand safety layers.

Instructions

Manage GAM CreativeWrapper entities — wrappers that inject scripts around all creatives served on an ad unit or placement.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5 credits. OUTPUT: Returns CreativeWrapper objects with id, name, adUnitId or placementId, headerHtmlSnippet, footerHtmlSnippet, and ordering. SIDE EFFECTS: Active CreativeWrappers apply globally to every creative served on the targeted ad unit/placement. Misconfigured wrappers can break ad serving. Test in a staging network first. WHEN TO USE: Use for injecting site-wide measurement scripts, viewability tags, or brand safety layers. Use presets for reusable wrapper templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • list: List all CreativeWrappers on the network. Read-only. • get: Get a specific CreativeWrapper by ID. Read-only. • create: Create a new CreativeWrapper. Write. Requires adUnitId or placementId, and headerHtmlSnippet or footerHtmlSnippet. • update: Update an existing wrapper's snippet or targeting. Write. • activate: Activate a paused wrapper. Write. • deactivate: Deactivate an active wrapper without deleting it. Write. Preferred over archive for temporary suspension. • archive: Archive a wrapper permanently. Destructive write. • set_data_declaration: Set the data usage declaration for a wrapper (required for GDPR/CCPA compliance). Write. • list_rich_media_ads_companies: List GAM-certified rich media companies available for wrapper configuration. Read-only. • find_third_party_company: Search for a third-party company by name to use in a wrapper. Read-only. • create_preset: Save a wrapper configuration as a reusable preset. Write. • list_wrapper_presets: List all saved wrapper presets. Read-only. • provision: Apply a preset to a set of ad units or placements. Bulk write.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
Behavior5/5

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

No annotations provided, so the description fully covers behavioral aspects: MODE (mixed read/write), AUTH (OAuth 2.0), CREDITS (0 for reads, 0.5 for writes), SIDE EFFECTS (global impact, risk of breaking ad serving), and a caution to test in staging. This exceeds typical disclosure.

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, etc.) and a usage recommendation. It front-loads the purpose. However, some phrases (e.g., 'CreativeWrapper' repetition) could be tightened without loss of clarity.

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?

The description covers return values (though no output schema), side effects, authentication, and credits. It is comprehensive given the tool's complexity. Minor gaps: lacks pagination details for list operations and error handling, but overall sufficient for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema descriptions for both parameters (action and network_code) are already detailed. The main description does not add extra meaning beyond what the schema provides, so it meets the baseline without improvement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool manages CreativeWrapper entities and explains they inject scripts around creatives. It distinguishes from siblings by specifying its GAM entity focus. However, the verb 'manage' is somewhat generic, though the sub-actions in the schema narrow it down.

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?

The description includes a 'WHEN TO USE' section specifying appropriate scenarios (e.g., injecting measurement scripts) and advises testing in staging due to side effects. It implicitly suggests using presets for templates, but does not explicitly contrast with sibling tools like creatives or inventory.

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