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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_segment_get

Read-onlyIdempotent

Retrieve a specific Google Ads audience segment by ID for a location and segment type to fetch its details.

Instructions

Get segment by ID Retrieve a specific Google Ads audience segment by ID Endpoint: GET /ad-publishing/google/segments/{segmentId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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": {
      "segmentId": "<segmentId>",
      "locationId": "<locationId>",
      "type": "<type>"
    },
    "name": "ghl_ad_google_segment_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesSegment type
segmentIdYesSegment identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant context: the required OAuth scope adPublishing.readonly and the v3 version header, which affect how the call must be authenticated and routed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and short, but the first two lines say the same thing twice ('Get segment by ID' / 'Retrieve a specific ... segment by ID'). The endpoint and scope lines are the only sentences that add value beyond the title.

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 single-resource fetch with full schema coverage and no output schema, the definition supplies endpoint, version, and auth scope, which is enough for correct invocation. Minor gap is the lack of guidance on enum type selection and error cases such as unknown segment IDs.

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 segmentId, locationId and the type enum are fully documented in the schema itself. The description adds nothing about the enum distinction between CUSTOM_SEGMENTS and DATA_SEGMENTS or the locationId scoping, 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 a Google Ads audience segment by ID. The 'by ID' phrasing implicitly distinguishes it from ghl_ad_google_segment_list, though no sibling is named explicitly.

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 only implied by 'by ID' and the endpoint path showing {segmentId}. There is no explicit statement of when to use this versus ghl_ad_google_segment_list or the offline_job/upsert variants, nor any preconditions about when a segment ID is known.

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