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

ghl-mcp-server-v2

by zackscriven

ghl_product_get

Read-onlyIdempotent

Retrieve a single product's details by product ID or slug and location ID, including optional wishlist status, to view or verify product information.

Instructions

Get Product by ID The "Get Product by ID" API allows to retrieve information for a specific product using its unique identifier. Use this endpoint to fetch details for a single product based on the provided product ID. Endpoint: GET /products/{productId} (Version header: v3; source: v3/products-v3.json) Requires an Agency or Sub-Account 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": {
      "productId": "<productId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_product_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesID or the slug of the product that needs to be returned
locationIdYeslocation Id
sendWishlistStatusNoParameter which will decide whether to show the wishlisting status of products

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context the annotations cannot carry: the Agency/Sub-Account token requirement, the products.readonly OAuth scope, the HTTP path and version header.

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 core purpose is front-loaded, but the description repeats itself across two sentences ('retrieve information ... using its unique identifier' vs 'fetch details ... based on the provided product ID') and pads with endpoint/version/source metadata that is mostly boilerplate.

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 simple single-resource GET with full schema coverage and no output schema, the definition supplies auth scope, token type and endpoint, which is enough for correct invocation. It does not hint at what the response contains, a minor gap given no output schema exists.

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 coverage is 100%, so productId (ID or slug), locationId and sendWishlistStatus are already documented in the schema. The description adds nothing about parameter formats or interactions, so the 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 ('Get Product by ID', 'retrieve information for a specific product using its unique identifier'), and the 'single product' framing implicitly contrasts with ghl_product_list. It never names a sibling explicitly, so it falls short of the top score.

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 fetch details for a single product based on the provided product ID' implies the when-to-use condition, but there are no exclusions or named alternatives (e.g. list vs. get vs. search). Usage is inferable rather than spelled out.

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