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

ghl-mcp-server-v2

by zackscriven

ghl_product_price_delete

DestructiveIdempotent

Delete a specific price from a product by providing the product ID, price ID, and location ID. Use it to remove outdated or incorrect product pricing from the system.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
priceIdYesID of the price that needs to be returned
productIdYesID of the product that needs to be used
locationIdYeslocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context the annotations don't carry: the required Agency or Sub-Account token and the products/prices.write OAuth scope. It stops short of saying whether the delete is permanent or what happens to references to the price.

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 operation, followed by compact metadata lines for endpoint, version, auth and scope that each earn their place. The second sentence repeats the title and the first sentence's content, which is minor padding but the definition stays short overall.

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

Completeness5/5

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

A three-parameter destructive tool with full schema coverage, complete annotations, no output schema, and explicit auth/scope requirements in the description. An agent has everything needed to authenticate and invoke it correctly; only edge-case semantics (cascade effects, error codes) are absent, which is acceptable here.

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, priceId and locationId are already documented in the input schema. The description's phrasing ('using its unique identifier', 'particular product') reinforces but does not extend that, 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?

States a specific verb and resource (delete a price belonging to a product) and pins it down with the exact REST path DELETE /products/{productId}/price/{priceId}. This distinguishes it implicitly from ghl_product_price_get/update/list/create, though no sibling is named 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?

'Use this endpoint to remove a price from the system' implies the usage but gives no when/when-not guidance or alternatives (e.g., whether to deactivate via ghl_product_price_update instead of deleting). The conditions under which deletion is the right choice versus updating are left to inference.

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