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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_targeting_search

Read-onlyIdempotent

Search Google Ads targeting options for geolocations or languages and retrieve identifiers to configure ad campaign targeting.

Instructions

Search targeting options Search Google geo-locations for ad targeting Endpoint: GET /ad-publishing/google/targeting/search (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": {
      "type": "<type>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_google_targeting_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesSearch type
queryNoSearch query
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "geolocation",
      +  "language"
      +]
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restatement. The description adds genuinely non-obvious context beyond annotations: the required OAuth scope (adPublishing.readonly) and the API endpoint/version, which matter for auth and debugging.

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 endpoint and scope kept as trailing metadata lines. Minor redundancy between the name-like first line ('Search targeting options') and the more specific second line.

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?

For a simple read-only, three-parameter search with full schema coverage and rich annotations, the definition gives enough to call it correctly. The notable gap is that it never describes what a search result looks like and there is no output schema, but this is a minor omission for a lookup tool.

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 the three parameters are already documented in the schema. The description adds nothing about parameter semantics and actually omits the 'language' search type, slightly underselling what the `type` enum accepts. Baseline 3 is appropriate.

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+resource (search Google geo-locations for ad targeting) and the platform qualifier 'Google' separates it from the family targeting-search siblings. However, the schema's `type` enum also supports 'language', which the description never mentions, so the stated scope is narrower than the tool's actual behavior.

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 use this versus alternatives — notably the sibling platform targeting searches (ghl_ad_fb_targeting_search, ghl_ad_li_targeting_search) or ghl_ad_google_target_interest_list. The agent must infer selection purely from the platform qualifier in the name.

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