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

ghl-mcp-server-v2

by zackscriven

ghl_product_store_set_priority

Set or update the display priority of products in a store by submitting product priority data for a location. Use it to control product ordering in store displays.

Instructions

Update product display priorities in store API to set the display priority of products in a store Endpoint: POST /products/store/{storeId}/priority (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token.

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": {
      "storeId": "<storeId>",
      "body": "<body>"
    },
    "name": "ghl_product_store_set_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
storeIdYesProducts related to the store

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateDisplayPriorityBodyDto"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent open-world call. The description adds useful operational context beyond that: the REST path, the v3 version header, and the required location token. It does not say whether calling it replaces all existing priorities or only the listed products, which is the key behavioral question for a reorder operation.

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?

It is short and the endpoint is front-loaded, but the first two lines say essentially the same thing ('Update product display priorities in store' / 'API to set the display priority of products in a store'). The duplication wastes space that could have carried ordering semantics.

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?

There is no output schema, so return values need not be explained, and the auth and endpoint metadata are present. But for a nested-body mutation with no annotations covering ordering semantics, the description should clarify what the priority array format means and whether unlisted products are affected; that omission leaves it only adequate.

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 schema already documents storeId and the nested body fields, making 3 the baseline. The description adds nothing about the semantics of the 'products' array (which is typed as an array of arrays in the schema and is genuinely ambiguous), so it does not compensate for the schema's weakest point.

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 ('Update product display priorities in store') and pins the exact endpoint, so an agent knows precisely what it mutates. It does not differentiate itself from the similarly named sibling ghl_product_store_set_inclusion, which also lives under product/store, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus related store/product tools, nor any when-not guidance. The only usage-adjacent content is the auth prerequisite ('Requires a Sub-Account (location) token'), which is a precondition rather than selection guidance.

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