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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_audience_member_remove

DestructiveIdempotent

Remove a single contact from a Facebook custom audience by specifying the custom audience ID plus locationId and contactId in the DELETE request body.

Instructions

Remove custom audience member Remove a single contact from a Facebook custom audience. Note this DELETE takes a request body carrying locationId and contactId, rather than identifying the member through the path or query. Endpoint: DELETE /ad-publishing/facebook/custom-audience/{customAudienceId}/member (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": {
      "customAudienceId": "<customAudienceId>",
      "body": "<body>"
    },
    "name": "ghl_ad_fb_audience_member_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
customAudienceIdYesCustom audience identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • removedInput schema / properties / audienceId
      Removed value: -{
      -  "description": "Custom audience identifier",
      -  "example": "23851234567890123",
      -  "type": "string"
      -}
    • addedInput schema / properties / body / title
      Added value: +"UpdateCustomAudienceDTO"
    • addedInput schema / properties / customAudienceId
      Added value: +{
      +  "description": "Custom audience identifier",
      +  "example": "23851234567890123",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "audienceId",
      -  "body"
      -]New value: +[
      +  "customAudienceId",
      +  "body"
      +]
  2. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint, but the description adds real value: the required OAuth scope (adPublishing.write), the exact endpoint and version header, and the non-obvious fact that this DELETE carries a request body. It does not state what the response looks like (no output schema), which keeps it from a 5.

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 action, then the critical call-shape note, then endpoint and scope metadata. No filler sentences, though the repeated title line at the top is mild redundancy.

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 destructive mutation tool the description covers endpoint, auth scope, and the tricky parameter placement, with annotations handling safety profile. Only omission is any indication of the response/return shape, which is minor since no output schema exists but callers may wonder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds genuinely useful semantics by explaining that locationId and contactId travel in the body rather than the path/query — a common source of invocation error for DELETE calls. It doesn't explain the optional fbAdAccountId, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Remove a single contact from a Facebook custom audience.' The 'single contact' scope cleanly distinguishes it from the batch sibling (ghl_ad_fb_audience_member_batch_update) and from add (ghl_ad_fb_audience_member_add) without needing to open schemas.

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

Usage Guidelines4/5

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

The single-member scope makes the intended use clear in contrast to the batch and add siblings, and the body-vs-path note warns how to call it. It stops short of an explicit 'use this when X, not Y' routing statement, so it earns a 4 rather than 5.

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