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

ghl-mcp-server-v2

by zackscriven

ghl_product_store_get_stats

Read-onlyIdempotent

Fetches product store statistics, including total, included, and excluded product counts, for a specific store to support catalog review and filtering analysis.

Instructions

Fetch Product Store Stats API to fetch the total number of products, included in the store, and excluded from the store and other stats Endpoint: GET /products/store/{storeId}/stats (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token. OAuth scopes: products.readonly

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>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_product_store_get_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
searchNoThe name of the product for searching.
altTypeYes
storeIdYesProducts related to the store
collectionIdsNoFilter by product collection Ids. Supports comma separated values

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: the auth requirement (sub-account/location token), the required OAuth scope, and the endpoint version. It does not describe pagination or response shape, but for a read-only stats call that is minor.

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?

The purpose is front-loaded in the first sentence, with auth and endpoint metadata following. The 'Endpoint:/Version header/source file' line is somewhat internal plumbing but is compact and does not bury the key information; nothing is filler-heavy.

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?

For a read-only stats endpoint with no output schema, the description does at least preview the returned counts (total/included/excluded), but it leaves 'other stats' undefined and never explains how the optional search and collectionIds filters change the result. Adequate, with a clear gap in return-value detail.

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 80%, so most parameters already carry documentation; the description only echoes storeId through the endpoint path template. It says nothing about altId, altType, search, or collectionIds, so it adds no semantic value beyond the schema. 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 (fetch) and resource (product store stats), and enumerates what is counted: total products, included, and excluded from the store. It never names a sibling to distinguish itself from ghl_product_store_set_inclusion or ghl_product_store_set_priority, and 'other stats' stays vague, so it stops just 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 Guidelines3/5

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

The prerequisites for calling are clear ('Requires a Sub-Account (location) token', 'OAuth scopes: products.readonly'), but there is no explicit statement of when to choose this tool over adjacent store tools, and no when-not guidance. Usage is only implied by the resource name.

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