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

ghl-mcp-server-v2

by zackscriven

ghl_media_create_folder

Creates a new media storage folder for a GoHighLevel sub-account location, with optional parent folder placement to organize uploaded assets.

Instructions

Create Folder Creates a new folder in the media storage Endpoint: POST /medias/folder (Version header: v3; source: v3/medias-v3.json) Requires a Sub-Account (location) token.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateFolderParams"
  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=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the description has a lower burden. It adds useful context by disclosing the auth requirement (location token) and the endpoint, but says nothing about duplicate-name behavior, whether parentId must reference an existing folder, or what happens on failure.

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?

Four short lines, front-loaded with the action. There is mild redundancy between the 'Create Folder' heading and 'Creates a new folder in the media storage', but the endpoint and version metadata that follow are compact and non-padded.

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?

There is no output schema, so the description would need to say what a successful create returns (presumably the new folder ID) for the agent to chain follow-up operations such as uploading into that folder. That return-value gap, plus the absence of duplicate/parent-folder semantics, leaves it only marginally complete for a mutation tool.

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% — name, altId, altType and parentId are each documented in the nested body schema. The description adds no parameter detail beyond the implicit location-token requirement, so the 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?

The description states a specific verb and resource plus the scope: 'Creates a new folder in the media storage'. The 'media storage' qualifier implicitly separates it from the many other folder-creation siblings (ghl_custom_field_create_folder, ghl_project_create_space_folder, ghl_email_template_folder_create), though it never names them explicitly.

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?

The prerequisite 'Requires a Sub-Account (location) token' is stated, which is a real usage constraint. However, there is no explicit guidance on when to choose this over other folder-creation tools, nor any exclusions or notes about the optional parentId vs root-level creation.

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