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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_conversion_goal_list

Read-onlyIdempotent

Fetch Google Ads conversion goals by location and paginate results using limit and pageToken.

Instructions

Get conversion goals Retrieve Google Ads conversion goals for a location. Without limit the response is a plain array. When limit is provided (max 100, default 100) the response is a paginated { conversionGoals, paging } envelope; pass pageToken (from paging.next) to fetch the next batch. Endpoint: GET /ad-publishing/google/conversion-goals (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_goal_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size for a paginated fetch (max 100, defaults to 100). When set, the response is a { conversionGoals, paging } envelope instead of a plain array.
pageTokenNoOpaque cursor for the next batch, taken from the previous response paging.next
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100, defaults to 100). When set, the response is a { conversionGoals, paging } envelope instead of a plain array.",
      +  "example": "100",
      +  "type": "string"
      +}
    • changedInput schema / properties / locationId / example
      Previous value: -"HChooFuiyPpVYzeJ4HMe"New value: +"loc_abc123"
    • 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 cover the read-only, idempotent, non-destructive profile, and the description adds substantive context: the response shape changes (plain array vs `{ conversionGoals, paging }` envelope) depending on `limit`, plus the OAuth scope and endpoint/version. It doesn't clarify what the default no-limit array size is, but the added behavioral detail clearly exceeds annotation coverage.

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 verb and resource, then pagination caveat, then endpoint/scope metadata. Mostly earns its place, but the final 'Pagination params' line is redundant with both the schema and the preceding sentence and could be cut.

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 read-only listing endpoint with full schema coverage and annotations, the description supplies the key operational facts an agent needs: the conditional response shape, the pageToken flow, the endpoint, and the required OAuth scope. No output schema exists, but the response envelope is described inline, so completeness is adequate.

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 all three parameters are already documented in the schema, including the limit/envelope interaction and the pageToken source. The description largely repeats this; the trailing 'Pagination params: limit — pass them to page through full result sets' adds no meaning and is slightly garbled, so the baseline 3 applies.

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 with scope: 'Retrieve Google Ads conversion goals for a location.' This distinguishes it reasonably well from the many sibling tools, though it never mentions the related ghl_ad_google_conversion_list / ghl_ad_google_conversion_get to clarify that this is specifically conversion *goals*, not conversions.

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?

Usage is implied and conditionally explained (pagination behavior based on `limit`), but there is no explicit 'use this when...' guidance and no comparison to the closely named sibling conversion tools. The agent must infer from locationId that this is a location-scoped listing call.

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