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

ghl-mcp-server-v2

by zackscriven

ghl_product_review_bulk_update

Bulk update multiple product reviews in one call, including setting statuses such as approved, to manage review moderation in batch.

Instructions

Bulk-mutates multiple reviews in one call (e.g. approve/reject in batch) — review the target reviewIds carefully before sending. Update Product Reviews Update one or multiple product reviews: status, reply, etc. Endpoint: POST /products/reviews/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_review_bulk_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / reviews / items / title
      Added value: +"UpdateProductReviewObjectDto"
    • changedInput schema / properties / body / properties / status / description
      Previous value: -"Status of the review"New value: +"Status to set on the reviews, e.g. 'approved'. (Spec bug override 2026-08-27: upstream declares this as an empty object schema despite listing it in required[] — the tool was uncallable. The spec enumerates no valid values; 'approved' is the documented example.)"
    • removedInput schema / properties / body / properties / status / example
      Removed value: -"approved"
    • changedInput schema / properties / body / properties / status / type
      Previous value: -"object"New value: +"string"
    • addedInput schema / properties / body / title
      Added value: +"UpdateProductReviewsDto"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the endpoint (POST /products/reviews/bulk-update), the required Sub-Account (location) token, and the products.write OAuth scope — exactly the auth context annotations cannot carry. It omits failure semantics (e.g. what happens if some reviewIds are invalid or partially succeed), which for a non-idempotent bulk mutation would be valuable.

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-loads the operation plus the safety warning, then the endpoint/auth metadata, which is the right order. There is some redundancy — the 'Update Product Reviews' line and 'Update one or multiple product reviews' restate the first sentence — but no filler beyond that.

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 single-body-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, it supplies the essentials: endpoint, auth token type, and OAuth scope. It is missing only bulk-specific behavior (shared status applied to all entries, partial-failure handling) and contains the stray 'reply' reference.

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 nested body fields are already documented; the description adds little beyond a caution about reviewIds and the 'approve/reject' example for status. It does mention 'reply' as a field being updated, which the schema does not expose, a mildly misleading detail. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: bulk-mutates multiple product reviews in one call (approve/reject in batch), and the 'one or multiple' phrasing implicitly separates it from the single-review sibling ghl_product_review_update. An agent can tell what it does and at what granularity without opening the schema.

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 'bulk-mutates multiple reviews in one call' framing implies when to use it, and the warning to review target reviewIds carefully is a useful precondition. However, it never states when NOT to use it or explicitly points to ghl_product_review_update for a single review, leaving routing to be inferred from the 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