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

ghl-mcp-server-v2

by zackscriven

ghl_product_review_update

Idempotent

Update a product review's status, reply, rating, or details by review ID to manage and moderate customer feedback.

Instructions

Update Product Reviews Update status, reply, etc of a particular review Endpoint: PUT /products/reviews/{reviewId} (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": {
      "reviewId": "<reviewId>",
      "body": "<body>"
    },
    "name": "ghl_product_review_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / reply / items / properties / user / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "email": {
      -        "description": "Email of the customer",
      -        "example": "example@example.com",
      -        "type": "string"
      -      },
      -      "isCustomer": {
      -        "description": "Is the person an admin or customer",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "name": {
      -        "description": "Name of the customer",
      -        "example": "John Doe",
      -        "maxLength": 100,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "phone": {
      -        "description": "Phone no of the customer",
      -        "example": "+1-555-555-5555",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name",
      -      "email"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "email": {
      +        "description": "Email of the customer",
      +        "example": "example@example.com",
      +        "type": "string"
      +      },
      +      "isCustomer": {
      +        "description": "Is the person an admin or customer",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "name": {
      +        "description": "Name of the customer",
      +        "example": "John Doe",
      +        "maxLength": 100,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "phone": {
      +        "description": "Phone no of the customer",
      +        "example": "+1-555-555-5555",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "email"
      +    ],
      +    "title": "UserDetailsDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / reply / items / title
      Added value: +"ProductReviewDto"
    • addedInput schema / properties / body / title
      Added value: +"UpdateProductReviewDto"
  2. 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 readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the exact endpoint, that a Sub-Account (location) token is required rather than an agency token, and the products.write OAuth scope. It does not clarify whether the PUT replaces or partially merges unspecified fields, which matters for a body with four required nested fields.

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 action and the mutable fields, followed by endpoint, token requirement and scope in a tight five-line block. The OpenAPI source citation ('source: v3/products-v3.json') is provenance scaffolding rather than agent-relevant information, a minor waste.

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?

For a two-parameter mutation tool with a fully-documented nested body and no output schema, the description supplies everything an agent needs to invoke it correctly: the operation, the endpoint, the required token type and the OAuth scope. Annotation coverage of the safety profile plus 100% schema coverage closes the remaining 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 every parameter including nested reply/user fields is already documented in the schema; baseline is 3. The description only echoes 'status, reply' and the {reviewId} path variable, adding no format, validation or bulk-vs-single semantics beyond the structured data.

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 ('Update ... a particular review') and names the mutable fields ('status, reply, etc'), which separates it from ghl_product_review_list, ghl_product_review_count, ghl_product_review_delete and ghl_product_review_bulk_update by name. It does not explicitly contrast against those siblings, 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-review mutation path, but there is no explicit 'use this instead of bulk_update when editing one review' guidance and no when-not conditions. The token/scope prerequisites are stated, but those are eligibility requirements 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