Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product reviews

ab_reviews
Read-onlyIdempotent

Fetch product reviews and customer questions with shop answers to check quality or get skin/hair care advice. Returns newest first, with ratings, verified buyer flags, and Jalali dates.

Instructions

Read customers' reviews and questions about a product (newest first) with the shop's answers.

Use as a quality check, or for the shop's skin/hair advice (staff answer questions with a recommended product). rating is null for a question; verified_buyer marks a confirmed purchase. Dates are Jalali (1405-07-13). Texts are cut at 400 chars (ending …) unless full_text=true. count and star_counts cover all reviews on the page; truncated=true means more than limit exist.

Input Schema

NameRequiredDescriptionDefault
limitNoMax reviews to return, newest first.
full_textNoReturn full review and reply texts, not 400-char cuts.
product_idYesAsal Banoo product id from ab_search / ab_browse, e.g. 6963.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return full review and reply texts, not 400-char cuts.",
+  "type": "boolean"
+}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / title
      Removed value: -"ab_reviewsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_reviewsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses 400-char truncation with the '…' marker and the full_text escape hatch, Jalali date format, rating=null meaning a question rather than a review, verified_buyer semantics, and the fact that count/star_counts cover the whole page while truncated=true signals more than `limit` exist. These are behavioral traits the annotations cannot convey.

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 core action in the first clause and packs semantic details into compact parentheticals with no filler. It is dense and slightly telegraphic, but every sentence carries information an agent needs.

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?

With no output schema, the description does the work of describing the return shape — rating, verified_buyer, count, star_counts, truncated, and the truncation marker — which is close to complete. It omits error behavior for an invalid product_id and any pagination path beyond a single limit, both minor gaps for a read tool with strong annotations.

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% (baseline 3), and the description adds genuine meaning on top of it: it ties full_text to the truncation rule and explains that the returned count/star_counts aggregates describe the page rather than the whole catalog. The exact limit semantics and product_id sourcing are largely left to the schema, which already documents them.

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 and resource: reads customer reviews and questions for a given product, with the shop's replies, newest first. That distinguishes it from siblings like ab_product and ab_search, which cover product data and discovery rather than user-generated review content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives two concrete use cases — quality check, and extracting the shop's skin/hair advice from staff answers. It does not explicitly name an alternative tool or state when not to use it, but the stated contexts are clear enough to route an agent.

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