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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_audience_get

Read-onlyIdempotent

Retrieve a specific Google Ads combined audience by audience ID and location ID to inspect targeting details for ad publishing.

Instructions

Get audience by ID Retrieve a specific Google Ads combined audience by ID Endpoint: GET /ad-publishing/google/audiences/{audienceId} (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": {
      "audienceId": "<audienceId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_google_audience_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceIdYesAudience 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, setting a lower bar. The description adds genuine context beyond that: the OAuth scope required (adPublishing.readonly) and the concrete endpoint/version, which helps an agent understand auth and API surface.

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 essential action and its qualification, then the endpoint and scope in compact form. The first two lines are near-redundant ('Get audience by ID' vs 'Retrieve a specific Google Ads combined audience by ID'), a small waste, but the rest is dense and useful.

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, so the description could describe what an audience object contains or what a not-found case looks like, and it does neither. It is adequate for routing and auth but leaves the return shape unspecified.

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 coverage is 100% and both parameters carry descriptions and examples, so the schema does the heavy lifting. The description adds nothing about audienceId format or locationId scoping semantics beyond restating that a specific audience is fetched, so the baseline 3 is appropriate.

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 states a specific verb+resource ('Retrieve a specific Google Ads combined audience by ID') and names the scope (Google Ads, combined audience). An agent can distinguish it from ghl_ad_google_audience_list and ghl_ad_google_audience_upsert without opening any schema.

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?

Retrieval-by-ID context is implied clearly, and the presence of the required audienceId parameter makes the use case obvious. However, there is no explicit guidance on when to prefer this over ghl_ad_google_audience_list or what happens if the ID is unknown (e.g., 404 behavior), so usage must be inferred.

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