Skip to main content
Glama
OrbiAds

OrbiAds

Official

audit_skill

Proactively detect ad delivery problems: hygiene issues, operational diagnostics, and compliance gaps. Six read-only sub-actions return severity-tagged findings with remediations.

Instructions

OrbiAds proactive audit suite — six sub-actions for quality and compliance analysis.

MODE: read-only (all actions are non-destructive analysis) AUTH: OAuth 2.0 required CREDITS: 0 (all actions free) OUTPUT: Returns a structured markdown report with findings, severity levels (CRITICAL/WARNING/INFO), and recommended remediations. WHEN TO USE: Use audit_skill to proactively detect problems before they impact delivery. • Use hygiene_check for routine health checks (orphaned creatives, stalled orders, mismatched budgets). • Use standards_baseline to verify compliance against a named framework (ISO 27001 ad-ops, IAB, NIST). • Use wrapper_coverage to audit creative wrapper deployment across ad units. • Use estimate_cost to preview credit costs before running expensive operations. NOT the same as audit: audit queries GAM change history; audit_skill analyzes current state. NOT the same as gam_audit: gam_audit is a convenience wrapper combining hygiene_check + ops_diagnostic + standards_baseline in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • hygiene_check: Scan the network for hygiene issues: orphaned creatives, line items past end date still active, orders with no live line items, creative-line item association gaps. Returns severity-tagged findings. • ops_diagnostic: Diagnose operational delivery problems: underdelivery, pacing issues, targeting conflicts, creative disapprovals. Correlates data across orders/line items/creatives. • standards_baseline: Evaluate the network against a named compliance framework. Requires framework parameter: orbiads_baseline | iso27001_adops | iab_anti_tampering | nist_csf. Returns a pass/fail checklist per control. • wrapper_coverage: Audit CreativeWrapper coverage across ad units and placements. Detects missing wrappers, double-wrapping, and wrapper misconfiguration. • estimate_cost: Preview the credit cost of an operation before executing it. Requires operation_name and parameters. Returns cost in credits and explanation. • export_authoring: Export an authoring-audit CSV of GAM entities (teams, users, custom fields, labels) for governance and compliance reporting. Returns a download URL or inline CSV.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
frameworkNoCompliance framework for standards_baseline action. Required when action=standards_baseline.
Behavior5/5

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

With no annotations, the description carries the full burden and excels: it declares read-only mode, OAuth 2.0 auth, zero credit cost, and structured markdown output with severity levels. This far exceeds typical transparency.

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, but somewhat verbose with bullet points that partially duplicate schema information. Still efficient and front-loaded with key facts.

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?

Without an output schema, the description fully explains the output format. It also covers authentication, cost, per-action details, prerequisites, and sibling comparisons, leaving no major gaps.

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?

Although schema coverage is 100% with detailed parameter descriptions, the tool description adds valuable usage context and when-to-use guidance for each action, going beyond mere schema repetition.

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 it is a proactive audit suite with six sub-actions for quality and compliance analysis. It explicitly distinguishes from sibling tools 'audit' and 'gam_audit', making its unique purpose unmistakable.

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 'WHEN TO USE' section provides specific guidance for each sub-action, and the description contrasts audit_skill with similar tools, giving clear criteria for when to choose it over alternatives.

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