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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_conversation_form_list

Read-onlyIdempotent

Retrieve Facebook conversation lead forms for a location, with optional pagination to fetch all forms in batches.

Instructions

Get conversation forms Retrieve Facebook conversation lead forms for a location. Without limit the response is a plain array. When limit is provided (max 100) the response is a paginated { conversationForms, paging } envelope; pass after (from paging.next) to fetch the next batch. Endpoint: GET /ad-publishing/facebook/conversation-forms (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_conversation_form_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOpaque cursor for the next batch, taken from the previous response paging.next
limitNoPage size for a paginated fetch (max 100). When set, the response is a { conversationForms, paging } envelope instead of a plain array.
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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": "25",
      +  "type": "string"
      +}
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100). When set, the response is a { conversationForms, paging } envelope instead of a plain array.",
      +  "example": "25",
      +  "type": "string"
      +}
    • changedInput schema / properties / locationId / example
      Previous value: -"HChooFuiyPpVYzeJ4HMe"New value: +"loc_abc123"
  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 cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real value: it discloses that the response shape changes depending on whether `limit` is passed, how the `after` cursor chains from `paging.next`, and the required adPublishing.readonly scope. Rate limits and error behavior are not covered, keeping it below a 5.

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 core behavior (conditional response shape) is front-loaded in the second sentence, and the endpoint/scope metadata is compact. The trailing 'Pagination params: limit — pass them to page through full result sets' line is redundant with earlier content and could be cut.

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?

There is no output schema, so the description carries the return-value burden and does so well by specifying both possible response shapes. With only three parameters, an endpoint, and an auth scope, an agent has everything needed to call it and interpret the result.

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 baseline is 3, and the description largely restates what the schema already documents (max 100, envelope vs array, `after` from paging.next). It does not add new semantics such as default page size or whether `limit` is a string vs number at the wire level.

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?

The description uses a specific verb and resource: 'Retrieve Facebook conversation lead forms for a location', which is far more precise than the name alone. It does not, however, distinguish this from adjacent siblings such as ghl_ad_fb_page_lead_form_list or ghl_ad_fb_lead_form_get, leaving the agent to infer which form type it needs.

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: the tool obviously lists forms for a location, and the pagination instructions tell the agent how to page. There is no 'use this when...' guidance, no exclusion of the page-level lead-form siblings, and no mention of prerequisites beyond the OAuth scope.

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