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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_account_list

Read-onlyIdempotent

Retrieve Google Ads accounts available to a connected user by location, including integration, ad manager, or email-matched sources.

Instructions

Get Google ad accounts Retrieve Google Ads accounts available for the connected user Endpoint: GET /ad-publishing/google/ad-accounts (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>"
    },
    "name": "ghl_ad_google_account_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoAccount source to read. `INTEGRATION` walks the connected user's MCC tree, `AD_MANAGER` returns the stored ad-manager integrations, `EMAIL` resolves the Google connection matching `email`. Defaults to `INTEGRATION`.INTEGRATION
emailNoGoogle account email to match a connection against. Required when `type=EMAIL`.
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "Google account email to match a connection against. Required when `type=EMAIL`.",
      +  "example": "user@example.com",
      +  "type": "string"
      +}
    • addedInput schema / properties / type / default
      Added value: +"INTEGRATION"
    • changedInput schema / properties / type / description
      Previous value: -"Account type"New value: +"Account source to read. `INTEGRATION` walks the connected user's MCC tree, `AD_MANAGER` returns the stored ad-manager integrations, `EMAIL` resolves the Google connection matching `email`. Defaults to `INTEGRATION`."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "INTEGRATION",
      -  "AD_MANAGER"
      -]New value: +[
      +  "INTEGRATION",
      +  "AD_MANAGER",
      +  "EMAIL"
      +]
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds real value by naming the required OAuth scope adPublishing.readonly and the endpoint/version header, but says nothing about result size, pagination, or what an empty account list means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly, but the first two lines restate the same idea (title and body), and the endpoint/source-file metadata is largely internal bookkeeping. The genuinely useful scope line is buried at the end.

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?

With no output schema, the description is the only place to learn what an account record contains or how results are shaped, and it does not say. For a listing tool with three query modes this leaves a real gap, though annotations and a fully documented schema cover the call mechanics.

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%, including an explicit description of the type enum and the email-required-when-type=EMAIL constraint, so the baseline is 3. The description adds nothing beyond the schema for any of the three parameters.

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?

It states a specific verb and resource (retrieve Google Ads accounts) and scopes them to the connected user. It is clear on its own but never distinguishes itself from ghl_ad_google_account_get or the parallel ghl_ad_fb_account_list / ghl_ad_li_account_list siblings, leaving platform and granularity routing to the name alone.

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 guidance on when to call this versus ghl_ad_google_account_get or the integration tools, and no mention of the three listing modes the tool supports. A caller must read the schema's type enum to discover that INTEGRATION vs AD_MANAGER vs EMAIL are meaningfully different queries.

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