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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_reporting_get

Read-onlyIdempotent

Retrieve Facebook campaign reporting for a date window by merging stored campaign data, Meta insights, and CDP-attributed contacts; use it to compare campaign metrics for published campaigns.

Instructions

Get campaign reporting Retrieve reporting for one campaign as a flat object, not the { grouped, totals } envelope the account-level report uses. Merges the locally stored campaign, Meta insights for the window, and CDP-attributed contacts. The campaign must be published — one without an fbCampaignId is rejected. Note results.lead (Meta lead actions) and leads (CDP attributed contacts) measure different things and routinely disagree. Endpoint: GET /ad-publishing/facebook/reporting/campaign/{campaignId} (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>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ghl_ad_fb_campaign_reporting_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesReport end date (YYYY-MM-DD)
startDateYesReport start date (YYYY-MM-DD)
campaignIdYesCampaign identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / campaignId / example
      Previous value: -"120208142050850608"New value: +"507f1f77bcf86cd799439011"
    • changedInput schema / properties / endDate / description
      Previous value: -"Report end date"New value: +"Report end date (YYYY-MM-DD)"
    • changedInput schema / properties / startDate / description
      Previous value: -"Report start date"New value: +"Report start date (YYYY-MM-DD)"
  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 readOnly/idempotent annotations, the description reveals the return shape, that multiple data sources are merged, the published-campaign prerequisite, and the important semantic disagreement between Meta lead actions and CDP-attributed contacts. These are material behavioral details an agent would not get from the annotations.

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 key distinction and prerequisites are front-loaded, and the caveat about `results.lead` vs `leads` is valuable. It is slightly verbose with the repeated 'Get campaign reporting' opener and endpoint/OAuth metadata, but nothing is seriously wasted.

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 reporting tool with no output schema, the description is complete enough: it explains the return shape, data sources, eligibility constraint, and a critical metric caveat. An agent has what it needs to invoke the tool correctly.

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 the schema already documents all four required parameters. The description adds some context about campaign eligibility and date-window reporting, but it does not meaningfully enrich each parameter beyond what the schema provides.

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: retrieve reporting for one campaign. It also explicitly distinguishes the result shape from the account-level report's `{ grouped, totals }` envelope, so an agent can tell this apart from related reporting tools.

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 gives a clear context for use and a prerequisite: the campaign must be published and have an `fbCampaignId`. It also implies the account-level report is an alternative, but it does not name that sibling tool or spell out when to choose aggregate reporting instead.

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