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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_segment_list

Read-onlyIdempotent

Retrieve Google Ads audience segments for a location, with optional pagination to fetch full result sets.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
typeNoSegment type
limitNoPage size for a paginated fetch (max 100, defaults to 100). When set, the response is a { segments, 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. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100, defaults to 100). When set, the response is a { segments, paging } envelope instead of a plain array.",
      +  "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"
      +}
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "CUSTOM_SEGMENTS",
      +  "DATA_SEGMENTS",
      +  "ALL"
      +]
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses a non-obvious behavioral quirk: the return shape changes based on whether limit is supplied (plain array vs { segments, paging } envelope), plus the pageToken source and max page size. This is exactly the kind of behavioral context annotations can't convey.

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-loads the core action and the pagination behavior early. The trailing endpoint/version/source metadata and the redundant 'Pagination params: limit' sentence are minor clutter but don't obscure the useful content.

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 paginated list tool with no output schema, the description covers what the agent needs: response shape, pagination mechanics, and auth scope. It could add selection guidance versus siblings, but operationally nothing essential is missing.

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 four parameters are already documented in the schema, including the limit response-shape behavior and pageToken source. The description largely restates these, adding little beyond the schema, so 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: 'Retrieve Google Ads audience segments for a location.' Clearly a list operation, distinguishable from segment_get/upsert/delete by name. It does not explicitly name the sibling it contrasts with, but the scope is unambiguous.

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?

Explains how to page through results (using limit and pageToken), which is usage-adjacent, but gives no guidance on when to use this tool versus alternatives like segment_get or audience_list. The reader must infer selection criteria.

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