Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_campaign_publish

Publishes a Google ad and pushes it live by submitting the ad ID and location ID.

Instructions

Publish ad Publish a Google ad and push it live Endpoint: POST /ad-publishing/google/ads/{adId}/publish (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adId": "<adId>",
      "body": "<body>"
    },
    "name": "ghl_ad_google_campaign_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesAd identifier
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body
      Added value: +{
      +  "description": "Request body (schema carried verbatim from the official OpenAPI spec).",
      +  "properties": {
      +    "locationId": {
      +      "description": "Location identifier",
      +      "example": "HChooFuiyPpVYzeJ4HMe",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "locationId"
      +  ],
      +  "title": "LocationIdBodyDTO",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "adId"
      -]New value: +[
      +  "adId",
      +  "body"
      +]
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Adds real context beyond the annotations by disclosing the required OAuth scope (adPublishing.write) and the API version header/spec source. However it doesn't state what the live push actually does on success, whether republishing an already-live ad is safe (annotations flag idempotentHint=false), or what state the ad must be in beforehand.

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?

Short and front-loaded, with the action stated first and the endpoint/scope metadata after. Minor redundancy between 'Publish ad' and 'Publish a Google ad and push it live', but nothing wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers action, endpoint, and auth scope for a non-idempotent, open-world mutation, but with no output schema there is nothing explaining what comes back — e.g. whether a publishing job identifier is returned for polling. An agent can invoke it correctly but cannot predict the result.

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 description coverage is 100%, so adId and locationId are already documented, and the endpoint template merely confirms adId is a path parameter. The description adds no field-level meaning, which is acceptable given the schema does the work.

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?

States a specific verb and resource ('Publish a Google ad and push it live') plus the concrete endpoint POST /ad-publishing/google/ads/{adId}/publish, which makes the scope unambiguous. It implicitly distinguishes itself from the Facebook equivalent (ghl_ad_fb_campaign_publish) by naming Google, but never explicitly routes to siblings such as ghl_ad_google_campaign_upsert or ghl_ad_google_get_publishing_progress.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to call this vs. upserting the campaign first, and no mention of the obvious follow-up sibling ghl_ad_google_get_publishing_progress for polling. The only hint of context is the OAuth scope line, which says what is required, not when to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools