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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_entity_get

Read-onlyIdempotent

Retrieve Facebook campaigns, ad sets, or ads for a location by entity type, with pagination to browse results.

Instructions

Get entities Retrieve campaigns, ad sets, or ads for a location. entityType selects which, and each returns a { data } envelope whose item shape differs — the id key is campaignId, adSetId, or adId respectively, and the status fields differ too: campaigns carry both status and effectiveStatus, ad sets only effectiveStatus, and ads only status. next is returned only when the branch pages through Meta, so treat its absence as the end of the results rather than assuming a cursor. For CAMPAIGN, type=INTEGRATION queries Meta while type=AD_MANAGER reads campaigns this service published, filtered to PAUSED and PUBLISHED. ADSET requires campaignId; AD accepts adSetId for a single ad set or campaignId to page across the campaign. Endpoint: GET /ad-publishing/facebook/entity (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>",
      "type": "<type>",
      "entityType": "<entityType>"
    },
    "name": "ghl_ad_fb_entity_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoPagination cursor
typeYesIntegration source type
adSetIdNoAd set identifier
fetchAllNoFetch all entities
searchIdNoSearch identifier
campaignIdNoCampaign identifier
entityTypeYesEntity type to fetch
locationIdYesLocation identifier
selectedAdAccountIdNoSelected ad account ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds substantial runtime detail: each branch returns a { data } envelope with different id and status fields, and next appears only when Meta pagination occurs. The guidance that missing next means end-of-results is exactly the kind of behavioral context an agent needs before calling.

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 description is front-loaded and dense with useful branch-specific information, with no obvious filler. It is a long single paragraph for a complex tool, but it generally earns its length; minor redundancy between 'Get entities' and 'Retrieve campaigns...' keeps it from being maximally concise.

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?

For a complex 9-parameter read tool with no output schema, the description covers the important return-shape differences, pagination semantics, and branch-specific filtering rules. Remaining gaps are the optional parameters like fetchAll and selectedAdAccountId, which are named in the schema but not meaningfully explained in the description.

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

Parameters4/5

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

Schema coverage is 100%, so parameter basics are already documented. The description still adds conditional meaning for entityType, type, campaignId, and adSetId, but it does not explain next, fetchAll, searchId, or selectedAdAccountId, so it is not fully comprehensive beyond the schema.

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 campaigns, ad sets, or ads for a location, with entityType selecting the branch. This is much more specific than the title 'Get entities' and lets an agent distinguish it from single-entity or other ad-platform getters in the sibling list.

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?

The description gives clear internal usage rules: ADSET requires campaignId, AD accepts either adSetId or campaignId, and CAMPAIGN's type changes whether Meta or service-published campaigns are read. It does not explicitly compare this tool with siblings such as ghl_ad_fb_campaign_get, so it falls short of the explicit alternatives/exclusions bar for 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