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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_publish

Queue a Facebook ad campaign for publishing to go live asynchronously, then check publishing progress to confirm Facebook IDs are attached.

Instructions

Publish campaign Queue a Facebook campaign for publishing and push it live to Facebook. Publishing runs asynchronously, so the campaign comes back in the state it was queued in — publishingStatus is still DRAFT on the campaign and on every ad set and ad, and no Facebook ids are attached yet. Poll GET /facebook/campaigns/{campaignId}/publishing-progress for the outcome. Endpoint: POST /ad-publishing/facebook/campaigns/{campaignId}/publish (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": {
      "campaignId": "<campaignId>",
      "body": "<body>"
    },
    "name": "ghl_ad_fb_campaign_publish"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"PublishAdDTO"
    • changedInput schema / properties / campaignId / example
      Previous value: -"120208142050850608"New value: +"507f1f77bcf86cd799439011"
  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?

Goes well beyond the annotations: discloses that publishing is asynchronous, that the returned campaign, ad sets and ads still show publishingStatus DRAFT, that no Facebook ids are attached yet, and that progress must be polled separately. It also names the OAuth scope (adPublishing.write) and the API version/source. Nothing about the mutation's side effects or eventual consistency is left for the agent to guess.

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 async caveat, then the poll instruction, then endpoint/scope metadata. Every sentence carries information, though the endpoint/version/source parenthetical is a little dense and could be trimmed. No filler or repetition.

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?

With no output schema, the description correctly compensates by describing exactly what the response looks like (DRAFT statuses, missing Facebook ids) and how to get the real outcome. The nested body object and OAuth requirement are both covered, so an agent has everything needed to call and interpret it.

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 description coverage is 100% and both parameters (campaignId, body.locationId) are documented in the schema, so the baseline is 3. The description adds no parameter-level meaning beyond the campaignId appearing in the endpoint path; it does not clarify what locationId governs in the publish context.

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 ("Queue a Facebook campaign for publishing and push it live to Facebook") and makes clear it is the publish action, not an upsert or a read. The endpoint line pins down the exact operation, so the agent can distinguish it from ghl_ad_fb_campaign_upsert and ghl_ad_fb_campaign_publishing_progress_get without inspecting 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?

Explicitly tells the agent what to do after invocation: poll GET /facebook/campaigns/{campaignId}/publishing-progress for the outcome. That effectively routes to the sibling tool. It does not state preconditions (e.g. campaign must already be created via upsert/draft state) or when not to publish, so it stops short of a full 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