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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_audience_update

Idempotent

Rename a Facebook custom audience or update its description for a location; changes are queued for reprocessing, so acknowledgement does not mean downstream state is current.

Instructions

Update custom audience Rename a Facebook custom audience or change its description. Only those two fields can be updated; membership is changed through the member endpoints. The audience is also queued for reprocessing, so the acknowledgement does not mean downstream state has caught up. Endpoint: PUT /ad-publishing/facebook/custom-audience/{customAudienceId} (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_update"
  }
}

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: +"FbUpdateAudienceBodyDTO"
    • 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.5/5.0
Behavior5/5

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

Goes well beyond the annotations, which only signal non-read-only, idempotent, non-destructive, open-world. It discloses the asynchronous reprocessing queue and warns that a successful acknowledgement does not mean downstream state has caught up — a genuinely important operational caveat not encoded anywhere else.

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 action and the key constraint before the endpoint/OAuth metadata block. The version-header and source-file metadata are marginally useful provenance rather than agent-facing guidance, but the body is tight overall.

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?

A mutation tool with no annotations-driven detail on side effects, yet the description covers updatable fields, exclusion of membership changes, required OAuth scope, and eventual consistency. Only the response payload is undescribed, which is acceptable given there is no output schema.

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 the baseline would be 3; the description earns extra by constraining semantics — only name and description are mutable, and membership is explicitly out of the payload's scope. It does not explain the locationId requirement or that name is mandatory, leaving that to the schema.

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 ("Rename a Facebook custom audience or change its description") and immediately delineates scope by excluding membership changes, which routes the agent away from the member siblings. The Facebook-ad prefix separates it from google/linkedin audience tools without ambiguity.

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?

"Only those two fields can be updated; membership is changed through the member endpoints" gives an explicit when-not and names the alternative tool family. It stops short of naming the exact sibling tool (e.g. ghl_ad_fb_audience_member_add/remove), but the context is clear enough to select correctly.

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