Skip to main content
Glama

create_product_review

Create a customer review for a specific product, used to add missing reviews or import historical review data.

Instructions

[WRITE] 建立單筆商品評論。

【用途】 為指定商品建立一筆顧客評論,適用於客服代為補登評論或匯入歷史評論資料。

【呼叫的 Shopline API】

  • POST /v1/product_review_comments

【回傳結構】 dict 含 success: bool, resource_id: str, message: str, review: dict。

【副作用】

  • 在商品評論列表中新增一筆評論,依商店設定可能立即公開或待審核

  • 影響商品的平均評分顯示

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
review_dataYes評論資料,例如 {"product_id": "P001", "rating": 5, "content": "品質很好!", "reviewer_name": "王小明"}
Behavior5/5

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

No annotations, so description fully handles transparency. Declares it's a write operation, lists side effects (public/pending, affects average rating), and provides return structure.

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?

Well-structured with sections, front-loaded verb, no wasted words. Each section adds distinct value.

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?

Covers purpose, use cases, API, return structure, and side effects. Minor omission of error handling or rate limits, but sufficient for the tool's simplicity.

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% with an example description, but the tool description adds no further parameter explanation. Baseline score is appropriate.

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?

Clearly states it creates a single product review, with use cases provided. Distinguishes from bulk_create_product_reviews sibling.

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?

Provides explicit use cases for customer service and historical data import. Does not explicitly exclude alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asgard-ai-platform/mcp-shopline'

If you have feedback or need assistance with the MCP directory API, please join our Discord server