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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_audience_member_batch_update

Idempotent

Add or remove Facebook custom audience members in bulk from a CSV or smartlists; queues the job and returns acceptance only.

Instructions

Batch update audience members Add or remove members in bulk from a Facebook custom audience, sourced from a CSV or one or more smart lists — at least one of csvPath or smartlistIds is required. The work is queued rather than performed inline, so the acknowledgement confirms only that the job was accepted; nothing about the outcome is reported here. Unlike the single-member endpoints this one answers with { success: true } rather than a status-and-message body. Endpoint: PUT /ad-publishing/facebook/custom-audience/{customAudienceId}/member/batch (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_batch_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. Changed5 schema fields changedv2.1.0
    • removedInput schema / properties / audienceId
      Removed value: -{
      -  "description": "Custom audience identifier",
      -  "example": "23851234567890123",
      -  "type": "string"
      -}
    • addedInput schema / properties / body / properties / operationType / enum
      Added value: +[
      +  "ADD",
      +  "REMOVE",
      +  "REPLACE"
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdateCustomAudienceBatchDTO"
    • 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?

Discloses traits the annotations do not: the work is queued rather than inline, the acknowledgement means only that the job was accepted, and no outcome is reported. It also notes the differing response body shape versus single-member endpoints and the required OAuth scope (adPublishing.write), which is exactly the contextual disclosure a mutation tool needs.

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 core action, then the source requirement, then the async caveat, then the endpoint/scope footer. Every sentence carries information, though the opening clause slightly restates the tool name before getting to the substantive detail.

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?

Covers the nested body's purpose, the source-selection requirement, the queueing behavior, and the return shape, which is sufficient given there is no output schema. The only gap is that per-operation semantics (what REPLACE does to existing members) are left entirely to the enum.

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 is 3, but the description adds a genuine constraint not encoded in the schema: the anyOf requirement that at least one of csvPath or smartlistIds be supplied. It does not explain the operationType semantics (ADD/REMOVE/REPLACE) or the dynamicAudience flag beyond the enum in the schema, so it is not a 5.

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 ('Batch update audience members', 'Add or remove members in bulk from a Facebook custom audience') and names the accepted sources of members. It also explicitly contrasts itself with the single-member endpoints, so an agent can distinguish it from ghl_ad_fb_audience_member_add/remove without opening a schema.

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?

Gives a concrete precondition ('at least one of csvPath or smartlistIds is required') and points to the single-member endpoints as the alternative for individual changes. It stops short of stating when a caller should prefer this tool over them in positive terms, but the routing signal is clear.

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