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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_audience_member_add

Idempotent

Add a single contact to a Facebook custom audience by resolving the contact ID and hashing identifiers before sending them to Meta; use the batch endpoint for multiple members.

Instructions

Add custom audience member Add a single contact to a Facebook custom audience. The contact is resolved from contactId and its identifiers are hashed before being sent to Meta. Use the batch endpoint for more than one member. Endpoint: PUT /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_add"
  }
}

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.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context beyond that: contact identifiers are resolved from contactId, hashed before being sent to Meta, and the operation requires adPublishing.write. It does not describe response behavior or failure cases, so it is strong but not exhaustive.

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?

The description is front-loaded with the core action and follows with relevant endpoint, auth, and alternative guidance. It is generally tight, though the repeated heading and the source JSON provenance add minor noise without helping an agent select or invoke the tool.

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 mutation tool with full schema coverage and annotations, the description supplies the key missing context: single-member scope, batch alternative, hashing behavior, endpoint, and OAuth scope. It does not cover return behavior, but no output schema exists and the core invocation guidance is complete enough.

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 description coverage is 100%, so the schema already documents the parameters, and the baseline would be 3. The description adds meaning beyond the schema by explaining that contactId is resolved and hashed and that customAudienceId is the path audience identifier. It does not explain the roles of locationId or fbAdAccountId beyond the schema, so it earns a 4 rather than 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?

The description states a specific verb and resource: adding a single contact to a Facebook custom audience. It immediately distinguishes this tool from the batch endpoint by saying to use batch for more than one member, so an agent can identify the correct tool without opening schemas.

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

Usage Guidelines5/5

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

It explicitly scopes usage to a single contact and names the alternative for multiple members: 'Use the batch endpoint for more than one member.' It also specifies the OAuth scope, making the write requirement 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