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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_page_list

Read-onlyIdempotent

Retrieve Facebook pages for a connected account, using optional limit and cursor pagination to fetch full page lists in batches.

Instructions

Get Facebook pages Retrieve Facebook pages for the connected account. Without limit the response is an array of pages (this array response will soon be deprecated — migrate to the paginated form). When limit is provided the response is a paginated { pages, paging } envelope; pass after (from paging.next) to fetch the next batch. Endpoint: GET /ad-publishing/facebook/pages (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_page_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOpaque cursor for the next batch, taken from the previous response paging.next
limitNoPage size for a paginated fetch (fetchExisting only, max 50). When set, the response is a { pages, paging } envelope instead of an array.
locationIdYesLocation identifier
fetchExistingNoFetch existing pages flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / after
      Added value: +{
      +  "description": "Opaque cursor for the next batch, taken from the previous response paging.next",
      +  "example": "QVFIU...",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (fetchExisting only, max 50). When set, the response is a { pages, paging } envelope instead of an array.",
      +  "example": "50",
      +  "type": "string"
      +}
  2. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuinely new behavioral facts: two response shape modes, an explicit deprecation of the array form, the pagination cursor contract, and the required OAuth scope adPublishing.readonly.

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 verb and resource, then the response-mode caveat, then endpoint/scope metadata. The trailing line 'Pagination params: limit — pass them to page through full result sets' is redundant with the preceding sentence and does not earn its place.

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?

With no output schema, the description compensates by describing both possible return shapes and the cursor path. Endpoint, version header, and OAuth scope are all present; only `fetchExisting` semantics and any rate/size caveats beyond the max-50 note are missing.

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 baseline is 3; the description goes beyond it by explaining the interaction between `limit` and `after` and how the two modes change the return shape, which the schema only states per-field. It leaves `fetchExisting` unaddressed, keeping it off a 5.

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 (Get/Retrieve) and resource (Facebook pages) scoped to the connected account, and the endpoint line pins the exact API path. It does not name the sibling it differs from (e.g. ghl_ad_fb_page_lead_form_list or ghl_ad_fb_page_delete), but the list semantics are unambiguous from the wording.

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 operational guidance: omit `limit` for the legacy array form, set `limit` for the paginated envelope, then pass `after` from `paging.next` for the next batch. It does not address when to prefer this over sibling page-scoped tools, so it stops short of full alternative routing.

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