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

ghl-mcp-server-v2

by zackscriven

ghl_course_import

Import complete course structures—including categories, posts, and materials—into a GoHighLevel location via the public courses import endpoint.

Instructions

COURSES API — the {productId} path parameter is the course (product) id. Import Courses Import Courses through public channels Endpoint: POST /courses/courses-exporter/public/import (Version header: v3; source: v3/courses-v3.json)

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_course_import"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / properties / contentType / enum
      Previous value: -[
      -  "video",
      -  "assignment",
      -  "quiz"
      -]New value: +[
      +  "video",
      +  "assignment",
      +  "quiz",
      +  "funnel"
      +]
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / properties / contentType / title
      Added value: +"contentType"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / properties / postMaterials / items / properties / type / title
      Added value: +"type"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / properties / postMaterials / items / title
      Added value: +"PostMaterialInterface"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / properties / visibility / title
      Added value: +"visibility"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / posts / items / title
      Added value: +"PostInterface"
    • changedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / properties / contentType / enum
      Previous value: -[
      -  "video",
      -  "assignment",
      -  "quiz"
      -]New value: +[
      +  "video",
      +  "assignment",
      +  "quiz",
      +  "funnel"
      +]
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / properties / contentType / title
      Added value: +"contentType"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / properties / postMaterials / items / properties / type / title
      Added value: +"type"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / properties / postMaterials / items / title
      Added value: +"PostMaterialInterface"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / properties / visibility / title
      Added value: +"visibility"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / posts / items / title
      Added value: +"PostInterface"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / properties / visibility / title
      Added value: +"visibility"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / subCategories / items / title
      Added value: +"SubCategoryInterface"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / properties / visibility / title
      Added value: +"visibility"
    • addedInput schema / properties / body / properties / products / items / properties / categories / items / title
      Added value: +"CategoryInterface"
    • addedInput schema / properties / body / properties / products / items / properties / instructorDetails / title
      Added value: +"InstructorDetails"
    • addedInput schema / properties / body / properties / products / items / title
      Added value: +"ProductInterface"
    • addedInput schema / properties / body / title
      Added value: +"PublicExporterPayload"
  2. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds only API plumbing (endpoint, version header, source file) rather than behavior. It never says whether importing creates new courses/products, overwrites existing ones, or is partially applied on failure — material for a non-idempotent bulk write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the API family, which is good. But a full sentence is spent on the nonexistent productId path parameter and another on internal provenance ('source: v3/courses-v3.json'), neither of which helps an agent call the tool.

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

Completeness2/5

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

For a non-idempotent bulk mutation with a 5-level nested payload and no output schema, the description should explain what the payload represents and what the endpoint does with it. Instead it gives endpoint metadata and one incorrect parameter note, leaving the agent unable to reason about the request body's required structure or the effect of the call.

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

Parameters2/5

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

The description references a '{productId} path parameter' that does not exist in the schema or in the stated endpoint (POST /courses/courses-exporter/public/import has no path params), which actively misleads about the inputs. The real input is a single deeply nested body (products → categories → subCategories → posts → postMaterials) whose properties carry no descriptions, and the description does nothing to explain that shape or the required locationId/products fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ('Import Courses') plus the concrete endpoint, so the agent knows it is a course-import mutation. But 'import' is never explained — it is unclear whether this bulk-creates courses from an exported payload, copies a snapshot from a public channel, or something else — and nothing distinguishes it from the many sibling course-creation tools (ghl_course_create, ghl_course_create_category, ghl_course_create_lesson).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no named alternative. An agent choosing between this and ghl_course_create or ghl_course_create_category has nothing to decide with; 'through public channels' hints at a source but never states the condition that selects this tool.

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