Skip to main content
Glama
OrbiAds

OrbiAds

Official

audit

Query Google Ad Manager change history to trace who modified orders, line items, creatives, or ad units and when the changes occurred.

Instructions

Query the GAM audit log for change history.

MODE: read-only AUTH: OAuth 2.0 required CREDITS: 0 (free) OUTPUT: Returns a list of AuditEvent objects with entityId, entityType, changeType, userId, timestamp, and a diff of changed fields. WHEN TO USE: Use audit when you need to trace who changed what and when on a specific GAM entity (order, line item, creative, ad unit). NOT the same as audit_skill: audit queries the GAM change log; audit_skill runs proactive quality/compliance checks. NOT the same as gam_audit: gam_audit runs a full network-wide compliance report; audit queries history for a specific entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • query_audit_log: Execute a filtered query against the GAM audit log. Filterable by entityId, entityType, userId, and date range. Returns a paginated list of audit events.
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?

No annotations provided, so description bears full burden. It discloses read-only mode, OAuth requirement, zero cost, and output format with fields. However, pagination is only mentioned in the input schema's action description, not in the main description.

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?

Well-structured with sections for mode, auth, credits, output, and usage guidance. Some redundancy in the 'NOT' comparisons, but overall efficient and front-loaded with purpose.

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?

Covers essential aspects: purpose, when to use, authentication, cost, output fields, and distinctions from similar tools. Lacks explicit pagination behavior and rate limits, but schema hints at pagination.

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%, baseline 3. Description adds value by listing filterable fields (entityId, entityType, userId, date range) that are only partially described in the schema's action parameter description.

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?

Description clearly states tool queries GAM audit log for change history, with explicit verb 'Query' and resource 'GAM audit log'. Differentiates from siblings audit_skill and gam_audit with specific contrasts.

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?

Provides explicit when-to-use: 'when you need to trace who changed what and when on a specific GAM entity'. Also specifies what it is not, naming alternative tools (audit_skill, gam_audit) and their purposes.

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