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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_audience_get

Read-onlyIdempotent

Retrieve a custom audience by ID with full detail, including subtype-specific fields and local source info for smart lists or CSV files.

Instructions

Get custom audience by ID Retrieve one custom audience with its full detail. Returns more than the listing endpoint: Meta adds the fields relevant to the audience subtype (retentionDays and customerFileSource for customer lists, rule and pixelId for website audiences, lookalikeSpec for lookalikes), and this service appends extras describing the local smart-list or CSV source when the audience is a user-provided customer list. Endpoint: GET /ad-publishing/facebook/custom-audience/{customAudienceId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_fb_audience_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation identifier
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 / customAudienceId
      Added value: +{
      +  "description": "Custom audience identifier",
      +  "example": "23851234567890123",
      +  "type": "string"
      +}
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "audienceId",
      -  "locationId"
      -]New value: +[
      +  "customAudienceId",
      +  "locationId"
      +]
  2. First observedv2.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses subtype-specific return fields (`retentionDays`, `customerFileSource`, `rule`, `pixelId`, `lookalikeSpec`) and the service-added `extras` field for local smart-list or CSV sources. It also states the endpoint and required OAuth scope, giving the agent useful behavioral context for a read-only retrieval.

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 purpose and is generally efficient, with each part contributing useful context about return differences, endpoint, and auth scope. The second sentence is dense but still earns its place by explaining subtype-specific response fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only get operation with annotations covering safety and no output schema, the description does the necessary work by explaining what the response adds over the listing endpoint and what extra fields may appear. It gives enough context to invoke the tool correctly without needing the output schema.

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 coverage is 100%, so both parameters are already documented. The description reinforces that retrieval is by `customAudienceId`, but it adds no syntax or format detail beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb and resource ('Get custom audience by ID', 'Retrieve one custom audience') and explicitly contrasts this with the listing endpoint, making it easy to distinguish from sibling audience operations.

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?

It clarifies that this is for retrieving a single audience with full detail and implies the listing endpoint is the alternative for broader retrieval. The when-to-use context is clear, though it does not explicitly state exclusions or that the listing endpoint is preferred for browsing.

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