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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_account_list

Read-onlyIdempotent

Retrieve Facebook ad accounts available to a connected user for a location, with optional account type filters and pagination to page through full result sets.

Instructions

Get ad accounts Retrieve Facebook ad accounts available for the connected user Endpoint: GET /ad-publishing/facebook/ad-accounts (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly Pagination params: limit — pass them to page through full result sets.

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>"
    },
    "name": "ghl_ad_fb_account_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoPagination cursor
typeNoAccount source type
limitNoResults page limit
fetchAllNoFetch all accounts
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "INTEGRATION",
      +  "AD_MANAGER"
      +]
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description usefully adds the required OAuth scope (adPublishing.readonly) and endpoint/version, but its pagination note only names 'limit' while silently ignoring the exposed `next` cursor and `fetchAll`, giving an incomplete picture of how to traverse results.

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 purpose is front-loaded in the first two lines and the ancillary metadata is compact. Some redundancy exists between 'Get ad accounts' and the following sentence, and the parenthetical version/source provenance is of limited use to an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with full annotation coverage and no output schema, the description covers the essentials. However, saying only 'Pagination params: limit' when a cursor parameter and a fetchAll flag also exist leaves an agent likely to miss the intended paging mechanism.

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 all five params are already documented, and the enum on `type` is self-describing. The description adds only that limit is a paging parameter and reinforces paging behavior; it says nothing about `type`, `next`, or `fetchAll` semantics. Baseline 3 applies.

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?

Concrete verb + resource: 'Retrieve Facebook ad accounts available for the connected user', which is materially clearer than the bare name and distinguishes it from the singular ghl_ad_fb_account_get. It never explicitly names siblings or the scope boundary (list vs. get vs. integration accounts) though.

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?

Usage is only implied by the phrase 'available for the connected user' and the read-only OAuth scope. There is no statement of when to prefer this over ghl_ad_fb_account_get, ghl_ad_fb_integration_get, or the Google/LinkedIn account-list siblings, and no prerequisite/eligibility guidance beyond the scope string.

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