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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_keyword_ideas_get

Retrieve keyword suggestions for Google Ads campaigns from a target URL, seed keywords, locations, and language to support ad targeting.

Instructions

Get keyword ideas Retrieve keyword suggestions for Google Ads campaigns Endpoint: POST /ad-publishing/google/keyword-ideas (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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_ad_google_keyword_ideas_get"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"KeywordSuggestionDTO"
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already give the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description usefully adds the concrete POST endpoint, the v3 version header, and the required OAuth scope adPublishing.readonly — real operational value. It does not explain why a read-style query is a non-idempotent POST or whether the call consumes Google Ads quota, so it stays at 3.

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?

Front-loaded with the action and resource in the first two lines; the endpoint/scope metadata is compact and useful rather than filler. The name/description/first-line triplet is slightly redundant ('Get keyword ideas' then 'Retrieve keyword suggestions'), costing a little tightness.

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?

There is no output schema, and the description never characterizes the return — whether it is a ranked list of keyword ideas, whether it includes suggested bids/volume, or roughly how many results to expect. For a nested-body, POST-based query tool, that leaves an agent guessing at the shape of the response.

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% and the nested KeywordSuggestionDTO documents url, keywords, locations, and languageCode individually, so the schema does the heavy lifting. The description adds no semantics beyond the schema — it does not say which of url/keywords is the primary seed or how locations and languageCode constrain results.

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 keyword suggestions for Google Ads campaigns'), which is unambiguous about what the tool produces. It does not explicitly differentiate itself from nearby siblings such as ghl_ad_google_targeting_search or ghl_ad_google_target_interest_list, which are the plausible confusions for an ad-targeting agent.

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

Usage Guidelines3/5

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

The description scopes usage to Google Ads campaigns, implying the domain in which to reach for it, but never says when to prefer it over the targeting-search or interest-list siblings, nor what prerequisites (an existing Google Ads integration/account) must hold before calling it.

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