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

ghl-mcp-server-v2

by zackscriven

ghl_product_bulk_update

Bulk-update multiple products in one call to adjust prices, availability, collections, or currency, or delete selected product IDs.

Instructions

Bulk-mutates multiple products in one call — review the target productIds carefully before sending. Bulk Update Products API to bulk update products (price, availability, collections, delete) Endpoint: POST /products/bulk-update (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) 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": {
      "body": "<body>"
    },
    "name": "ghl_product_bulk_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / compareAtPrice / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "roundToWhole": {
      -        "description": "Round to nearest whole number",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "description": "Type of price update",
      -        "enum": [
      -          "INCREASE_BY_AMOUNT",
      -          "REDUCE_BY_AMOUNT",
      -          "SET_NEW_PRICE",
      -          "INCREASE_BY_PERCENTAGE",
      -          "REDUCE_BY_PERCENTAGE"
      -        ],
      -        "example": "INCREASE_BY_AMOUNT",
      -        "type": "string"
      -      },
      -      "value": {
      -        "description": "Value to update (amount or percentage based on type)",
      -        "example": 100,
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "value"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "roundToWhole": {
      +        "description": "Round to nearest whole number",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "description": "Type of price update",
      +        "enum": [
      +          "INCREASE_BY_AMOUNT",
      +          "REDUCE_BY_AMOUNT",
      +          "SET_NEW_PRICE",
      +          "INCREASE_BY_PERCENTAGE",
      +          "REDUCE_BY_PERCENTAGE"
      +        ],
      +        "example": "INCREASE_BY_AMOUNT",
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "Value to update (amount or percentage based on type)",
      +        "example": 100,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "value"
      +    ],
      +    "title": "PriceUpdateField",
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / body / properties / filters / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "availableInStore": {
      -        "description": "Filter by availability status",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "collectionIds": {
      -        "description": "Filter by collection IDs",
      -        "example": [
      -          "5f8d0d55b54764421b7156c1",
      -          "5f8d0d55b54764421b7156c2"
      -        ],
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "productType": {
      -        "description": "Filter by product type",
      -        "example": "one-time",
      -        "type": "string"
      -      },
      -      "search": {
      -        "description": "Filter by search term",
      -        "example": "blue t-shirt",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "availableInStore": {
      +        "description": "Filter by availability status",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "collectionIds": {
      +        "description": "Filter by collection IDs",
      +        "example": [
      +          "5f8d0d55b54764421b7156c1",
      +          "5f8d0d55b54764421b7156c2"
      +        ],
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "productType": {
      +        "description": "Filter by product type",
      +        "example": "one-time",
      +        "type": "string"
      +      },
      +      "search": {
      +        "description": "Filter by search term",
      +        "example": "blue t-shirt",
      +        "type": "string"
      +      }
      +    },
      +    "title": "BulkUpdateFilters",
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / body / properties / price / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "roundToWhole": {
      -        "description": "Round to nearest whole number",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "description": "Type of price update",
      -        "enum": [
      -          "INCREASE_BY_AMOUNT",
      -          "REDUCE_BY_AMOUNT",
      -          "SET_NEW_PRICE",
      -          "INCREASE_BY_PERCENTAGE",
      -          "REDUCE_BY_PERCENTAGE"
      -        ],
      -        "example": "INCREASE_BY_AMOUNT",
      -        "type": "string"
      -      },
      -      "value": {
      -        "description": "Value to update (amount or percentage based on type)",
      -        "example": 100,
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "value"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "roundToWhole": {
      +        "description": "Round to nearest whole number",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "description": "Type of price update",
      +        "enum": [
      +          "INCREASE_BY_AMOUNT",
      +          "REDUCE_BY_AMOUNT",
      +          "SET_NEW_PRICE",
      +          "INCREASE_BY_PERCENTAGE",
      +          "REDUCE_BY_PERCENTAGE"
      +        ],
      +        "example": "INCREASE_BY_AMOUNT",
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "Value to update (amount or percentage based on type)",
      +        "example": 100,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "value"
      +    ],
      +    "title": "PriceUpdateField",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"BulkUpdateDto"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

The description adds useful operational context (POST endpoint, location-token requirement, products.write scope, and the caution about productIds), which annotations do not carry. However, it explicitly lists "delete" as a supported bulk operation while annotations declare destructiveHint=false, sending conflicting safety signals for a non-idempotent bulk mutation. It also says nothing about whether bulk updates are partial-failure tolerant or how selectAll/filters interact with productIds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The caution is front-loaded, which is good, but the body then repeats the title twice ("Bulk Update Products" / "API to bulk update products") before the substantive endpoint and auth lines. Some of the OpenAPI provenance text (source file path) earns little for an agent and could be trimmed.

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?

Auth requirements, scope, and the endpoint are given, which matters for this API. But for a destructive-capable, non-idempotent bulk mutation with a nested body and no output schema, the description leaves out response shape, partial-failure behavior, and how filters/selectAll relate to explicit productIds. Adequate but with real gaps.

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 the enum of operation types and the nested price/compareAtPrice objects are already fully documented. The description reinforces that productIds is the crucial input and that price/availability/collections are the mutatable dimensions, but adds no syntax, precedence, or format guidance beyond the schema. Baseline 3 is appropriate.

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 opening sentence states a specific verb+resource+scope: bulk-mutates multiple products in one call, covering price, availability, collections, and delete. The endpoint and scope lines reinforce that this is a write operation on products rather than a single-record update. It never names the closest siblings (ghl_product_bulk_edit, ghl_product_update, ghl_product_review_bulk_update), so the agent must infer differentiation itself.

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?

"Review the target productIds carefully before sending" is a safety caution rather than a when-to-use rule, and the token/scope lines are prerequisites. There is no explicit statement of when to prefer this over ghl_product_update or ghl_product_bulk_edit, nor when each of the five operation types (price, availability, collection, delete, currency) should be chosen.

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