Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Product reviews

tl_reviews
Read-onlyIdempotent

Read a product's customer reviews with average rating, star distribution, AI pros/cons summary, and sortable review pages to surface complaints or recent feedback.

Instructions

Read customer reviews of a product: average 0-5, star distribution, AI summary with pros/cons, and the reviews.

sort=lowest_rated surfaces complaints (rating sorts rank the newest 500 reviews). The AI summary (null for few reviews) is on page 0 only.

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": {
      "product_code": "<product_code>"
    },
    "name": "tl_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page number.
sortNoReview order.newest
limitNoReviews per page.
full_textNoReturn review and reply text uncut (default cuts at 400 chars).
product_codeYesProduct code, e.g. 'TLP-60492' (bare number works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / full_text / description
      Previous value: -"Return review and reply text uncut (default cuts at 400 characters)."New value: +"Return review and reply text uncut (default cuts at 400 chars)."
    • changedInput schema / properties / sort / description
      Previous value: -"Order of the reviews."New value: +"Review order."
  2. Changed8 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Return review and reply text uncut (default cuts at 400 characters).",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • changedInput schema / properties / product_code / description
      Previous value: -"Product code from a search or list, e.g. 'TLP-60492' (the bare number works too)."New value: +"Product code, e.g. 'TLP-60492' (bare number works)."
    • removedInput schema / properties / product_code / title
      Removed value: -"Product Code"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"tl_reviewsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_reviewsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses non-obvious behavior: rating sorts rank the newest 500 reviews, the AI summary is null for few reviews, and the summary appears only on page 0. These are valuable caveats not captured by annotations, though auth or rate-limit behavior is not addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, first stating what is returned and then adding the most important sort and pagination caveats. Every sentence contributes useful information without unnecessary wording.

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 read-only review-fetching tool with five well-documented parameters and no output schema, the description sufficiently covers return contents, sorting behavior, and AI summary availability. No critical calling information appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining that sort=lowest_rated surfaces complaints and that rating-based sorts operate over the newest 500 reviews. It also clarifies that the AI summary is tied to page 0, adding context beyond the schema.

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?

The description uses a specific verb and resource: "Read customer reviews of a product." It also names the returned data components, making the tool clearly about product reviews rather than shop reviews, so it is distinguishable from the sibling tl_shop_reviews.

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?

It offers useful operational guidance such as using sort=lowest_rated to surface complaints and notes that the AI summary appears only on page 0. However, it does not explicitly say when to use this tool instead of alternatives like tl_shop_reviews or tl_product.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.