Skip to main content
Glama
OrbiAds

OrbiAds

Official

campaign

Automate the full lifecycle of ad orders and line items in Google Ad Manager — from draft creation to deployment, updates, pause, archive, and rollback.

Instructions

Orchestrate GAM campaign lifecycle — the primary write surface for creating and managing campaigns.

MODE: write-heavy (most actions modify GAM data) AUTH: OAuth 2.0 required CREDITS: deploy = 2–5 credits depending on line item count. Other write operations = 0.5–1 credit. Reads = 0. CONFIRMATION TOKEN: create_draft, deploy and rollback require a confirmation_token obtained from a prior dry-run preview. This prevents accidental deployment. DEPLOY WORKFLOW: create_draft creates a Firestore campaigns/{campaignId} document from MCP. deploy accepts either campaignId (modern campaigns/{id}) or jobId (legacy jobs/{id}). For direct GAM-only display trafficking, use create_display. OUTPUT: deploy returns {campaign_id, order_id, line_item_ids[], creative_ids[], status}. rollback returns {reverted_to_version, entities_affected}. SIDE EFFECTS: deploy creates Order + LineItems + Creatives + LICAs in GAM — irreversible without rollback. rollback archives the current version and restores the previous one. WHEN TO USE: Use campaign for end-to-end campaign creation from a blueprint. Use line_items or orders for surgical updates to existing campaigns. DESTRUCTIVE: rollback and archive are non-trivial — they modify live GAM entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdNoLegacy Firestore jobs/{jobId} document. deploy also accepts modern campaignId.
actionYesSub-operation to perform: • deploy: Deploy a complete campaign to GAM: accepts campaignId from create_draft/REST or legacy jobId, plus confirmation_token. Creates Order, LineItems, Creatives, and LICAs. • create_draft: Create an OrbiAds campaigns/{campaignId} draft from MCP without using the web UI. Write, requires confirmation_token. • update: Update an existing campaign's metadata, budget, or targeting without full redeployment. Write. • ensure_template: Ensure a native ad template exists in GAM, creating it if absent. Idempotent write. • create_native_style: Create a GAM native ad style for use in native campaigns. Write. • create_line_items_batch: Create multiple line items under an existing order in one call. Write. Faster than individual line item creation. • create_licas: Create LineItem-Creative Associations (LICAs) to link creatives to line items. Write. • create_display: Create a standard display ad campaign (order + line items + creatives) from a template. Write, requires confirmation_token. • rollback: Revert a campaign to its previous deployed version. Destructive write — archives current version. Requires confirmation_token. • pause: Pause all active line items in a campaign. Write. • archive: Archive a campaign (order + line items). Destructive — removes from active serving. Requires confirmation_token.
campaign_idNoOrbiAds campaigns/{campaignId} identifier, accepted by deploy and campaign lifecycle actions.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
confirmation_tokenNoWrite-confirmation token from a prior estimate/preview call. Required for deploy, rollback, archive.
Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses write-heavy nature, OAuth requirement, credit costs, confirmation token necessity, side effects (irreversible deployment), and destructive actions (rollback, archive). This goes well beyond minimal disclosure and fully informs the agent of behavioral traits.

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 front-loaded with the key purpose. It is fairly long but every sentence adds value. Minor redundancy in repeating confirmation token info across sections.

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 explicitly states the output format for deploy and rollback. It also covers side effects, destructive actions, and prerequisites. For a complex tool with many sub-operations, this is comprehensive and complete.

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 description coverage is 100%, so baseline is 3. The description adds workflow context (e.g., why confirmation_token is needed, how deploy works) that complements the schema's parameter descriptions. While the schema already details each parameter, the description's additional context justifies a slightly higher score.

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's purpose: 'Orchestrate GAM campaign lifecycle — the primary write surface for creating and managing campaigns.' It uses a specific verb ('orchestrate') and resource ('GAM campaign lifecycle'), and distinguishes itself from sibling tools like line_items and orders by specifying when to use each.

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 guidance is provided: 'Use campaign for end-to-end campaign creation from a blueprint. Use line_items or orders for surgical updates to existing campaigns.' This tells the agent when to use this tool versus alternatives, which is exactly what this dimension requires.

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