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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_publishing_progress_get

Read-onlyIdempotent

Poll a campaign's Meta publishing progress, including completed steps and completion state, so validation UIs can track an in-flight publish.

Instructions

Get campaign publishing progress Returns Redis-backed publish progress for a campaign while it is publishing to Meta. Used by the validation funnel UI to poll step counts and completion state. Endpoint: GET /ad-publishing/facebook/campaigns/{campaignId}/publishing-progress (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": {
      "campaignId": "<campaignId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_fb_campaign_publishing_progress_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesCampaign identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  2. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and openWorld, but the description adds genuinely non-obvious behavior: the data is Redis-backed and tied to an in-flight publish, plus the required OAuth scope adPublishing.readonly and the concrete endpoint. It does not say what happens when polling after completion (error vs. stale/empty result), which is the main remaining behavioral gap.

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?

Purpose and timing are front-loaded in the first two sentences, with endpoint/scope metadata relegated to a trailing block. The version-header and source-file parenthetical is somewhat operational noise for an agent, but overall the text is tight and well ordered.

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?

With no output schema, the description compensates by naming what comes back ('step counts and completion state'), which is exactly what an agent needs to interpret results. It also documents auth scope and endpoint. Only the absent-publish edge case is missing, so it is close to complete for a simple two-parameter polling tool.

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% for both campaignId and locationId, so the schema carries the parameter burden. The description only surfaces campaignId via the endpoint path template and adds no format, scoping, or location-relationship detail beyond that, so baseline 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 opens with a specific verb+resource ('Get campaign publishing progress') and immediately narrows the scope: Redis-backed progress for a campaign while it publishes to Meta. This clearly separates it from ghl_ad_fb_campaign_publish (which initiates publishing) and from ghl_ad_fb_campaign_get (final campaign state), so an agent can place it without opening the 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?

It states the operative condition ('while it is publishing to Meta') and the consumer pattern ('Used by the validation funnel UI to poll step counts'), which tells an agent when polling is appropriate. It stops short of naming an explicit alternative for after publishing completes or stating what to do if no publish is in flight, so it is clear context rather than full when/when-not guidance.

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