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

ghl-mcp-server-v2

by zackscriven

ghl_product_delete

DestructiveIdempotent

Deletes a product from GoHighLevel by product ID and location ID, removing it from the system when it is no longer needed.

Instructions

Delete Product by ID The "Delete Product by ID" API allows deleting a specific product using its unique identifier. Use this endpoint to remove a product from the system. Endpoint: DELETE /products/{productId} (Version header: v3; source: v3/products-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: products.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": {
      "productId": "<productId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_product_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesID or the slug of the product that needs to be returned
locationIdYeslocation Id
sendWishlistStatusNoParameter which will decide whether to show the wishlisting status of products

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 destructiveHint=true and idempotentHint=true, so the description's added value is the operational context: the raw DELETE /products/{productId} route, the v3 version header, the source spec file, the required Agency or Sub-Account token, and the products.write OAuth scope. That is real auth/routing information not present in the annotations. It stops short of saying whether dependent entities (prices, reviews, collections) are also removed, which is the one behavior an agent would still want.

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?

Front-loaded with the action and target, with the endpoint, version, and scope metadata in compact trailing lines. The duplication of 'Delete Product by ID' as both a heading and an inline phrase is mild waste but the whole thing stays scannable.

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 three-parameter destructive tool with no output schema, the description covers the route, auth model, and scopes, while annotations handle the safety profile. The remaining gap is cascade/irreversibility detail, which is a notable but not fatal omission.

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 productId, locationId, and sendWishlistStatus are already documented. The description adds nothing to the parameters and doesn't clarify that productId accepts a slug as well as an ID, so the baseline 3 applies.

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 ('Delete Product by ID') and reiterates the act of removing a product by unique identifier. An agent can immediately distinguish it from ghl_product_update, ghl_product_get, or ghl_product_bulk_edit.

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?

Says to use this endpoint 'to remove a product from the system,' which implies the use case, but there are no when-not conditions, no mention of alternatives (e.g. archive vs. hard delete), and no prerequisites spelled out beyond the token requirement.

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