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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_conversion_delete

DestructiveIdempotent

Deletes a Google Ads conversion action by conversion ID for a specified location, enabling cleanup of outdated or incorrect conversion tracking in GoHighLevel.

Instructions

Delete conversion Delete a Google Ads conversion action by ID Endpoint: DELETE /ad-publishing/google/conversions/{conversionId} (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": {
      "conversionId": "<conversionId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_google_conversion_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation identifier
conversionIdYesConversion identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / conversionId / example
      Previous value: -"conv_abc123"New value: +"123456789"
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  2. First observedv2.0.0

TDQS

A4/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 openWorldHint=true, so the safety profile is covered. The description contributes additional operational context beyond them: the required OAuth scope 'adPublishing.write' and the v3 API version/source, which materially affects whether a call will succeed.

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 action and endpoint, and the metadata lines are compact. Minor redundancy between the title-like first line 'Delete conversion' and the following sentence, but nothing wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full schema coverage and rich annotations, the description supplies everything else an agent needs: the resource path, version header, and required OAuth scope. No output schema exists, so nothing about return values is owed.

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% and both parameters (locationId, conversionId) are documented in the schema; the description only maps conversionId to the path placeholder. No extra semantics or format hints are added, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete a Google Ads conversion action by ID') and pins it to the exact endpoint DELETE /ad-publishing/google/conversions/{conversionId}. This cleanly separates it from the sibling conversion_get/list/upsert tools in the ad_google family.

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 destructive intent and the 'by ID' requirement make the use case inferable, but there is no explicit guidance on when to prefer this over alternatives (e.g., getting the ID via ghl_ad_google_conversion_list, or using conversion_upsert to modify rather than remove). No exclusions or prerequisites are stated.

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