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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_conversion_list

Read-onlyIdempotent

Retrieve Google Ads conversion actions for a location. Choose AD_MANAGER for full actions with pagination or AD_WORDS for a minimal projection.

Instructions

Get conversions Retrieve Google Ads conversion actions for a location. The response shape is selected by type. When type is AD_MANAGER: without limit a plain array of full conversion actions, and with limit (max 100, default 100) a paginated { conversions, paging } envelope — pass pageToken (from paging.next) for the next batch. When type is omitted or AD_WORDS, a different, minimal snake_case projection is returned and limit, pageToken, startDate, endDate, conversionType and category are all ignored. Endpoint: GET /ad-publishing/google/conversions (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly Pagination params: limit — pass them to page through full result sets.

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_conversion_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoIntegration type
limitNoPage size for a paginated fetch (max 100, defaults to 100). When set, the response is a { conversions, paging } envelope instead of a plain array. Applies to AD_MANAGER type only.
endDateNoFilter end date
categoryNoConversion action category to filter by
pageTokenNoOpaque cursor for the next batch, taken from the previous response paging.next
startDateNoFilter start date
locationIdYesLocation identifier
conversionTypeNoConversion action type to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • changedInput schema / properties / category / description
      Previous value: -"Conversion category"New value: +"Conversion action category to filter by"
    • addedInput schema / 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 / conversionType / description
      Previous value: -"Conversion type"New value: +"Conversion action type to filter by"
    • addedInput schema / properties / conversionType / enum
      Added value: +[
      +  "UPLOAD_CLICKS",
      +  "UPLOAD_CALLS",
      +  "WEBPAGE",
      +  "LEAD_FORM_SUBMIT",
      +  "AD_CALL"
      +]
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100, defaults to 100). When set, the response is a { conversions, paging } envelope instead of a plain array. Applies to AD_MANAGER type only.",
      +  "example": "100",
      +  "type": "string"
      +}
    • addedInput schema / properties / pageToken
      Added value: +{
      +  "description": "Opaque cursor for the next batch, taken from the previous response paging.next",
      +  "example": "100",
      +  "type": "string"
      +}
  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 readOnlyHint/idempotentHint, so the safety profile is covered. The description goes further and discloses the two distinct response shapes, the paging envelope, and the surprising fact that six parameters are silently ignored for AD_WORDS — behavior an agent could not learn from the schema alone.

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 then the response-shape branching, which is the right order. The trailing endpoint, OAuth scope, and pagination lines are boilerplate but short and informative; the middle sentence is dense but earns its length.

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?

With no output schema, the description must carry the burden of describing returns, and it does so reasonably well by explaining the polymorphic response shapes and pagination envelope. It leaves some gaps (what fields appear in the 'minimal snake_case projection', error behavior), but an agent can call it correctly.

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 the schema already documents every parameter, and the description's parameter notes (limit max/default, pageToken source, ignored filters) largely restate them. It adds marginal consolidation value, but not meaning beyond the structured fields.

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 Google Ads conversion actions for a location'), which is far more precise than the bare title 'Get conversions'. It does not, however, distinguish itself from sibling ghl_ad_google_conversion_get or ghl_ad_google_conversion_goal_list, so an agent must infer the boundary from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives conditional guidance tied to the `type` parameter (which response shape you get, and which params are ignored under AD_WORDS), which is genuinely useful. But it never states when to call this tool versus the sibling conversion_get or conversion_goal_list, so usage relative to alternatives is only implied.

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