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

ghl-mcp-server-v2

by zackscriven

ghl_media_delete_file

DestructiveIdempotent

Deletes a specific file or folder from GoHighLevel media storage using its ID and location token, allowing unwanted media assets to be removed.

Instructions

Delete File or Folder Deletes specific file or folder from the media storage Endpoint: DELETE /medias/{id} (Version header: v3; source: v3/medias-v3.json) Requires a Sub-Account (location) token. OAuth scopes: medias.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": {
      "id": "<id>",
      "altType": "<altType>",
      "altId": "<altId>"
    },
    "name": "ghl_media_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
altIdYeslocation Id
altTypeYesAltType

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds meaningful operational context: the exact endpoint, API version, required sub-account token, and OAuth scope. It does not explain whether folder deletion cascades to contents, but it adds substantial value beyond the annotations.

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 description is short and front-loads the action and resource, followed by endpoint and auth details. There is minor redundancy between the title line and the first sentence, but overall it is efficient and well-structured.

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 destructive delete tool with annotations covering safety and no output schema, the description supplies the essential auth, scope, endpoint, and version context. It leaves some edge-case behavior unstated, such as recursive folder deletion semantics, but it is complete enough for an agent to invoke it correctly.

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 67%, with altId and altType minimally described and id undocumented. The description indirectly clarifies id via DELETE /medias/{id} and relates the sub-account token to the location context, but it does not fully compensate for the schema's remaining ambiguity around altType and altId.

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: it deletes a file or folder from media storage, and it gives the underlying DELETE /medias/{id} endpoint. It does not explicitly distinguish this single-item delete from sibling ghl_media_bulk_delete_files, so it is clear but not fully sibling-differentiated.

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?

It provides useful invocation context by stating that a Sub-Account (location) token is required and naming the medias.write OAuth scope. However, it does not say when to use this rather than ghl_media_bulk_delete_files or other media operations, so usage is implied rather than explicitly guided.

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