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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_campaign_get

Read-onlyIdempotent

Retrieve a Facebook campaign with its linked adsets and ads using campaign and location IDs. Use it to inspect campaign structure and associated entities.

Instructions

Get campaign with linked entities Retrieve a Facebook campaign with its linked adsets and ads Endpoint: GET /ad-publishing/facebook/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>"
    },
    "name": "ghl_ad_fb_campaign_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated field names
sourceNoCampaign data source
campaignIdYesCampaign identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / campaignId / example
      Previous value: -"120208142050850608"New value: +"507f1f77bcf86cd799439011"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description goes beyond them by disclosing the OAuth scope (adPublishing.readonly), the API version header, and that the response includes linked adsets and ads — genuinely useful behavioral detail. Pagination or missing-campaign error behavior is not mentioned.

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 and compact: intent first, then endpoint, then required scope. The first two lines are slightly redundant ('Get campaign with linked entities' vs. 'Retrieve a Facebook campaign with its linked adsets and ads'), but nothing else is 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 single-record getter with no output schema and fully documented parameters, the definition supplies everything an agent needs: what is returned (campaign plus adsets/ads), the exact endpoint, and the auth scope. There is no complex mutation or nested schema left unexplained.

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%, so the schema already documents all four parameters; baseline 3 applies. The description's 'linked adsets and ads' phrase loosely connects to the `fields` example 'adsets,ads', hinting that field expansion drives linked entity inclusion, but it never explains that relationship or the `source` parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieve a Facebook campaign, and clarifies the scope as 'with its linked adsets and ads'. That distinguishes it from the reporting, publishing-progress and upsert siblings, though it does not name or contrast with them explicitly (e.g. ghl_ad_fb_entity_get).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The endpoint line and required campaignId imply 'fetch one campaign by id', so the usage context is inferable. However, there is no statement of when to prefer this over ghl_ad_fb_entity_get, ghl_ad_fb_campaign_reporting_get, or the upsert tool, and no prerequisites beyond the scope hint.

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