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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_reporting_list

Read-onlyIdempotent

Retrieve Facebook campaign, ad set, or ad reporting metrics for a location and date range; use a campaign ID for ad set and ad lists.

Instructions

Get reporting list Retrieve campaigns, ad sets, or ads with their reporting metrics. listType selects the entity and changes the item shape; adsets and ads additionally require campaignId. Entities Meta has no insights for are still returned, padded with a fixed zero row that carries fewer fields than a real one. Note none is accepted by validation but has no handler and fails with a 409. Deprecated: use GET /ad-publishing/facebook/reporting/rows with header version: v4. Endpoint: GET /ad-publishing/facebook/reporting/list (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": {
      "locationId": "<locationId>",
      "listType": "<listType>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "type": "<type>"
    },
    "name": "ghl_ad_fb_reporting_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesIntegration source type
endDateYesReport end date (YYYY-MM-DD)
listTypeYesReporting list type
startDateYesReport start date (YYYY-MM-DD)
campaignIdNoCampaign identifier (required when listType is adsets or ads)
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / endDate / description
      Previous value: -"Report end date"New value: +"Report end date (YYYY-MM-DD)"
    • addedInput schema / properties / listType / enum
      Added value: +[
      +  "ads",
      +  "adsets",
      +  "campaigns",
      +  "none"
      +]
    • 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.7/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds real behavior beyond them: entities without Meta insights are returned padded with a fixed zero row carrying fewer fields, and `none` passes validation but has no handler and fails with a 409. It also discloses the version header and required OAuth scope.

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 core capability and the highest-value caveats (zero-padding, the `none` trap, deprecation) in tight sentences. The redundant leading 'Get reporting list' line restates the name/title and could be dropped, but the rest earns its place.

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 still characterizes the return shape (real rows vs. fixed zero rows with fewer fields), the version/endpoint, auth scope, and deprecation status. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning the schema cannot: listType changes the item shape, adsets/ads cross-require campaignId, and `none` is a validated-but-broken enum value. That trap warning alone materially improves correct parameter selection.

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 ('Retrieve campaigns, ad sets, or ads with their reporting metrics') and immediately distinguishes itself from the single-entity reporting siblings by describing list semantics and per-listType item shapes. An agent can tell this apart from ghl_ad_fb_reporting_get without opening either 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?

Gives clear conditional usage: listType selects the entity, and adsets/ads additionally require campaignId. It also flags the tool as deprecated in favor of a newer endpoint/version, which is a strong routing signal. It stops short of explicitly contrasting with sibling tools like ghl_ad_fb_campaign_reporting_get, so not a 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