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

ghl-mcp-server-v2

by zackscriven

ghl_product_collection_delete

DestructiveIdempotent

Delete a specific product collection by its collection ID and location token. Removes the specified collection from the sub-account to manage product data.

Instructions

Delete Product Collection Delete specific product collection with Id :collectionId Endpoint: DELETE /products/collections/{collectionId} (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token. OAuth scopes: products/collection.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": {
      "collectionId": "<collectionId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_product_collection_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id
altTypeYesThe type of alt. For now it is only LOCATION
collectionIdYesMongoId of the collection

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?

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds context the annotations cannot: the exact endpoint, API version header (v3), source spec, and required auth scope. It does not say what happens to products inside the collection when it is deleted, which is the one notable gap for a destructive operation.

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, then endpoint, auth, and scope in short lines that each carry information. The repeated 'Delete Product Collection' line echoing the title is mildly redundant but the definition stays tight.

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 single-entity destructive delete with no output schema and full parameter coverage, the description supplies everything needed to invoke it: endpoint, version header, required token type, and OAuth scope. Only the side effects of deletion remain undisclosed.

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 all three parameters (altId, altType, collectionId) are already documented in the schema. The description only calls out collectionId by name and adds nothing on altId/altType or the LOCATION enum, so 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 names a specific verb and resource (delete a product collection) and pins scope to a single collection by collectionId, so the agent knows exactly what the call does. It does not explicitly contrast with sibling collection tools such as ghl_product_collection_update or ghl_product_collection_get, so differentiation is left to the name.

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: delete a collection when you have its MongoId. The description states prerequisites (sub-account/location token, the products/collection.write scope) but gives no when-to-use versus alternatives or when not to call it. Adequate but with a clear gap.

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