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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_campaign_get

Read-onlyIdempotent

Retrieve a specific Google Ads campaign by ID and location to inspect campaign details, configuration, or reporting context.

Instructions

Get Google campaign by ID Retrieve a specific Google Ads campaign by ID Endpoint: GET /ad-publishing/google/ads/{adId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_google_campaign_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesAd identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new context in the OAuth scope ('adPublishing.readonly') and version header, but says nothing about error behavior when the adId is unknown or whether the response is cached/scoped.

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 purpose is front-loaded in the first line, and the endpoint/scope metadata is compact and useful. The second line largely restates the first ('Retrieve a specific Google Ads campaign by ID' vs 'Get Google campaign by ID'), which is minor redundancy.

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?

For a two-parameter read tool with full schema coverage and no output schema, this is adequate but thin: it never hints at what the campaign payload includes or how locationId affects the lookup, leaving the agent to discover those at call time.

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 both adId and locationId are already documented in the schema. The description reinforces that lookup is by ad ID via the URL template but never mentions locationId, adding nothing beyond the schema baseline.

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 ('Retrieve a specific Google Ads campaign by ID') and pins it to the GET endpoint, so an agent knows exactly what it returns. It does not, however, explicitly distinguish itself from nearby siblings such as ghl_ad_google_campaign_upsert or ghl_ad_fb_campaign_get; the agent must infer that from the name.

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?

There is no statement of when to use this versus the upsert/publish siblings, nor any prerequisite (e.g. that the campaign must already exist or that locationId must match the ad's owner). Usage is only implied by the phrase 'by ID'.

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