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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_conversation_form_create

Creates a Facebook Messenger conversation form for a GoHighLevel location with a welcome message and quick-reply questions, enabling ad-driven conversations.

Instructions

Create conversation form Create a Messenger conversation form. Note the created record is returned in its raw stored form rather than the shape the listing endpoint uses: the identifier comes back as _id instead of id, and the internal __v version key is included. Endpoint: POST /ad-publishing/facebook/conversation-forms (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

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": {
      "body": "<body>"
    },
    "name": "ghl_ad_fb_conversation_form_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / questions / items / title
      Added value: +"WelcomeMessageQuestion"
    • addedInput schema / properties / body / title
      Added value: +"CreateConversationFormDTO"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-idempotent, open-world write. The description adds genuinely non-obvious behavior: the created record comes back in raw stored form with `_id` instead of `id` and an internal `__v` key, plus the required `adPublishing.write` scope. That is real value beyond the annotations, though it does not cover failure modes.

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 return-shape warning is front-loaded and the endpoint/scope metadata is compact. The leading 'Create conversation form' line duplicates the title slightly, a small redundancy but not a structural problem.

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 create tool with no output schema, the description wisely explains the actual response shape quirk that would otherwise mislead an agent parsing the result, and it names the required scope. Missing only a note on validation failures or whether duplicates are allowed, which is minor.

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% and the single nested body object documents name, text, questions, and locationId with examples, so the schema carries the semantics. The description adds nothing about parameter meaning or the required nested fields, which is the expected baseline here.

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?

States a specific verb and resource ('Create a Messenger conversation form') with the platform scope made explicit. It is trivially distinguishable from the sibling ghl_ad_fb_conversation_form_list, which is the read counterpart.

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 agent can infer this is the write path for ad-publishing conversation forms from the endpoint line and the contrast with the listing endpoint. There is no explicit statement of when to choose this tool, no prerequisites beyond the OAuth scope, and no exclusions.

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