Skip to main content
Glama
OrbiAds

OrbiAds

Official

creative_qa

Run compliance checks, SSL validation, tracking audits, and tag syntax verification on creatives before activation. Get pass/fail reports with remediation guidance.

Instructions

Creative quality assurance — validate, scan, and pre-check creatives before and after trafficking.

MODE: read-only (all actions are non-destructive analysis) AUTH: OAuth 2.0 required CREDITS: 0 (all free) OUTPUT: Returns a QA report with pass/fail status per check, severity (CRITICAL/WARNING/INFO), and specific issue descriptions with remediation guidance. WHEN TO USE: Run creative_qa after uploading creative assets and before activating line items. Use pre_archive_check before archiving a creative to detect active associations. NOT the same as audit_skill: audit_skill checks network-wide operational health; creative_qa focuses specifically on individual creative compliance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • scan_creative_compliance: Scan a creative for policy violations, prohibited content, missing click-through URLs, and size non-compliance. Returns a compliance report per check. • validate_creative_ssl: Verify that all URLs in a creative (click-throughs, image src, tracking pixels) are HTTPS. Critical for modern GAM requirements. • validate_creative_ssl_batch: Run SSL validation on multiple creatives in one call. Returns a per-creative summary. • audit_creative_tracking: Verify all impression and click tracking pixels are reachable and return 200. Detects broken trackers. • audit_order_tracking: Audit tracking pixels across all creatives associated with an order. Returns a per-creative, per-tracker report. • validate_tag_snippet: Validate a third-party ad tag snippet for syntax errors, unsafe JS, and missing required macros (%%CLICK_URL%%, etc.). • pre_archive_check: Check whether a creative has active LICA associations before archiving. Returns list of active line items that would be affected.
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?

With no annotations, the description fully discloses behavior: 'MODE: read-only (all actions are non-destructive analysis)', 'AUTH: OAuth 2.0 required', 'CREDITS: 0 (all free)', and output format explained. Each sub-action's behavior is detailed in enum descriptions.

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 a brief intro, metadata in key-value pairs, usage guidelines, and differentiation. It is slightly lengthy but each sentence adds value; the structure aids readability.

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?

Despite no output schema, the description explains the output. It covers purpose, usage, auth, credits, output, and sub-actions thoroughly. All necessary context for an agent to select and invoke the tool correctly is present.

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

Parameters5/5

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

Schema coverage is 100%, and description adds value: action enum values have detailed descriptions, and network_code includes example and source instructions. The overall description also provides context that enhances parameter understanding.

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 'Creative quality assurance — validate, scan, and pre-check creatives before and after trafficking' and lists specific actions via enum. It distinguishes from sibling 'audit_skill' by specifying that audit_skill checks network-wide health while creative_qa focuses on individual creative compliance.

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?

Explicit usage guidance: 'Run creative_qa after uploading creative assets and before activating line items. Use pre_archive_check before archiving a creative to detect active associations.' Also notes that it is not the same as audit_skill, providing clear when-to-use and when-not-to-use.

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