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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_conversion_upsert

Idempotent

Create or update a Google Ads conversion action for a location, including category, value settings, counting, attribution, and click-through window.

Instructions

Upsert conversion Create or update a Google Ads conversion action Endpoint: PUT /ad-publishing/google/conversions (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": {
      "body": "<body>"
    },
    "name": "ghl_ad_google_conversion_upsert"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / category / description
      Previous value: -"Conversion category"New value: +"Conversion action category"
    • addedInput schema / properties / body / properties / category / enum
      Added value: +[
      +  "DEFAULT",
      +  "PAGE_VIEW",
      +  "PURCHASE",
      +  "SIGNUP",
      +  "LEAD",
      +  "DOWNLOAD",
      +  "ADD_TO_CART",
      +  "BEGIN_CHECKOUT",
      +  "SUBSCRIBE_PAID",
      +  "PHONE_CALL_LEAD",
      +  "IMPORTED_LEAD",
      +  "SUBMIT_LEAD_FORM",
      +  "BOOK_APPOINTMENT",
      +  "REQUEST_QUOTE",
      +  "GET_DIRECTIONS",
      +  "OUTBOUND_CLICK",
      +  "CONTACT",
      +  "ENGAGEMENT",
      +  "STORE_VISIT",
      +  "STORE_SALE",
      +  "QUALIFIED_LEAD",
      +  "CONVERTED_LEAD"
      +]
    • changedInput schema / properties / body / properties / type / description
      Previous value: -"Conversion type"New value: +"Conversion action type. Only `UPLOAD_CLICKS` is supported — the conversion list endpoint reads back UPLOAD_CLICKS actions only, so a conversion created with any other type would never be returned."
    • changedInput schema / properties / body / properties / type / enum
      Previous value: -[
      -  "UPLOAD_CLICKS",
      -  "UPLOAD_CALLS",
      -  "WEBPAGE",
      -  "LEAD_FORM_SUBMIT"
      -]New value: +[
      +  "UPLOAD_CLICKS"
      +]
    • changedInput schema / properties / body / properties / type / example
      Previous value: -"WEBPAGE"New value: +"UPLOAD_CLICKS"
    • changedInput schema / properties / body / properties / valueSettings / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "alwaysUseDefaultValue": {
      -        "description": "When true, always uses the default value even if a transaction-specific value is provided",
      -        "example": false,
      -        "type": "boolean"
      -      },
      -      "defaultCurrencyCode": {
      -        "description": "ISO 4217 currency code for the default value",
      -        "example": "USD",
      -        "type": "string"
      -      },
      -      "defaultValue": {
      -        "description": "Default monetary value assigned to each conversion",
      -        "example": 10,
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "defaultValue",
      -      "defaultCurrencyCode",
      -      "alwaysUseDefaultValue"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "alwaysUseDefaultValue": {
      +        "description": "When true, always uses the default value even if a transaction-specific value is provided",
      +        "example": false,
      +        "type": "boolean"
      +      },
      +      "defaultCurrencyCode": {
      +        "description": "ISO 4217 currency code for the default value",
      +        "example": "USD",
      +        "type": "string"
      +      },
      +      "defaultValue": {
      +        "description": "Default monetary value assigned to each conversion",
      +        "example": 10,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "defaultValue",
      +      "defaultCurrencyCode",
      +      "alwaysUseDefaultValue"
      +    ],
      +    "title": "ConversionValueSettings",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpsertConversionDTO"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds genuinely useful context: the OAuth scope adPublishing.write and the required v3 version header. However, the central behavioral question for an upsert — how the server decides create vs. update (presumably the optional conversionId) and whether existing settings are overwritten — is never addressed.

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?

Four short lines, front-loaded with the verb and resource before endpoint/scope metadata. The 'Upsert conversion' line largely duplicates the tool title, but the rest is dense and non-redundant.

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?

For a single-body mutation with full schema coverage, annotations, and no output schema, the description covers auth and endpoint but leaves the upsert matching rule and any return behavior unexplained. That gap matters more than usual here because the tool can silently modify an existing conversion action.

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 the nested UpsertConversionDTO documents every field with examples, so the schema carries the parameter burden. The description adds no field-level meaning of its own; its only extra information is transport-level (PUT endpoint, v3 header), which is not a parameter in the schema.

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 pair ('Create or update') and a precise resource ('a Google Ads conversion action'), which cleanly separates it from siblings like ghl_ad_google_conversion_get, ghl_ad_google_conversion_list, and ghl_ad_google_conversion_delete. An agent can identify the tool from the first two lines without opening the 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?

The 'upsert' verb implies the create-or-update case, but the description never says when to prefer this over ghl_ad_google_conversion_get/list or when an update is warranted versus a fresh create. No prerequisites, no exclusions, no named alternative — usage is only inferable from the tool name.

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