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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_account_delete

DestructiveIdempotent

Remove a Google Ads account connection from a location by deleting the specified ad account. Provide the ad account ID and location ID to disconnect ad publishing access.

Instructions

Delete ad account Remove a Google Ads account connection from a location Endpoint: DELETE /ad-publishing/google/ad-accounts/{adAccountId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

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": {
      "adAccountId": "<adAccountId>",
      "body": "<body>"
    },
    "name": "ghl_ad_google_account_delete"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"LocationIdBodyDTO"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds useful behavioral context beyond those annotations by naming the exact endpoint, version header, required OAuth scope adPublishing.write, and by clarifying that this removes a connection from a location rather than necessarily deleting the underlying Google Ads account.

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?

The description is short and front-loads the action and resource before endpoint and auth metadata. The opening 'Delete ad account' is slightly redundant with the more precise second line, and the source-file reference is developer metadata rather than agent-facing guidance, but overall the text is efficient.

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 destructive delete with annotations covering safety and idempotency and a fully described schema, the description provides enough context: what is removed, the endpoint, and the required OAuth scope. It does not describe side effects on campaigns or return behavior, but no output schema exists and deletion tools often omit that detail.

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 both adAccountId and the nested locationId are already documented in the input schema. The endpoint path reinforces that adAccountId is the primary target and the body carries location context, but the description adds no other parameter-level semantics.

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 uses a specific verb and resource: it deletes an ad account and clarifies that this means removing a Google Ads account connection from a location. That distinction helps separate it from sibling account get/list tools and from tools operating on underlying Google Ads campaigns.

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 operation is clearly a deletion of a Google Ads account connection, so the implied use case is disconnecting that account from a location. However, the description does not explicitly state when to use this versus alternatives such as account get/list or integration deletion, nor does it state prerequisites beyond the OAuth scope.

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