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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_account_get

Read-onlyIdempotent

Retrieve details for a specific Google Ads account using its ad account ID and location ID, so you can inspect account configuration and status.

Instructions

Get ad account details Retrieve details of a specific Google Ads account Endpoint: GET /ad-publishing/google/ad-accounts/{adAccountId} (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>",
      "adAccountId": "<adAccountId>"
    },
    "name": "ghl_ad_google_account_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation identifier
adAccountIdYesAd account 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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the description isn't obligated to restate safety. It does add real value beyond them: the OAuth scope 'adPublishing.readonly' (an auth requirement the agent may need to satisfy) and the concrete GET endpoint. It omits error behavior for unknown/adAccountId not found.

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 core action, and the endpoint/scope metadata is genuinely useful for an agent. However, 'Get ad account details' and 'Retrieve details of a specific Google Ads account' are two sentences saying the same thing, which is minor waste.

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 two-parameter read tool with full annotation coverage and no output schema, the description covers what it does, where it lives, and what auth it needs. Only the return shape and failure modes are unaddressed, which is acceptable given the tool's simplicity.

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%, so both locationId and adAccountId are already documented in the schema; baseline 3 applies. The description surfaces adAccountId via the endpoint path template but adds no format guidance beyond the schema's 'act_abc123' example.

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 details of a specific Google Ads account'), which is enough to distinguish a single-account fetch from the sibling ghl_ad_google_account_list. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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 phrase 'a specific Google Ads account' implies this is the lookup-by-id counterpart to a list operation, but there is no explicit when-to-use/when-not guidance, no note that adAccountId must come from the list endpoint, and no mention of required prior setup.

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