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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_segment_delete

DestructiveIdempotent

Delete a Google Ads audience segment by ID using its segment type and location to remove unwanted segments from ad publishing.

Instructions

Delete segment Delete a Google Ads audience segment by ID Endpoint: DELETE /ad-publishing/google/segments/{segmentId} (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": {
      "segmentId": "<segmentId>",
      "locationId": "<locationId>",
      "type": "<type>"
    },
    "name": "ghl_ad_google_segment_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesSegment type
segmentIdYesSegment identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is carried by structured data. The description's only added context is the required OAuth scope 'adPublishing.write' and the v3 version header; it does not say whether deletion is permanent, whether segments attached to live campaigns are affected, or what the response contains.

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?

Short and front-loaded: the action is clear in the first clause and the endpoint/scope metadata trails it. The opening 'Delete segment' line is redundant with the title and the following sentence, a minor waste.

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 simple three-parameter delete with full schema coverage and a rich annotation set, the definition covers what the agent needs to invoke it: resource, ID, endpoint, and authorization scope. Only the consequences of deletion (irreversibility, effect on running campaigns) are absent.

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 (segmentId, locationId, type with its two-value enum) are already documented. The description restates only that deletion is by ID and adds no format or constraint details beyond the schema.

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+resource ('Delete a Google Ads audience segment by ID') and pins down the API surface with the DELETE endpoint path. It is distinct from segment_get/list/upsert by name, but it never explicitly contrasts itself with the sibling that would otherwise be used to modify a segment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to delete versus when to use ghl_ad_google_segment_upsert or offline_job_create, and no warning about prerequisites beyond the OAuth scope. The agent must infer usage entirely 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