Skip to main content
Glama

delete_product_review

Permanently delete a product review from your Shopline store. Removes violations, malicious or test reviews, updating comment count and average rating.

Instructions

[WRITE] 刪除單筆商品評論。

【用途】 從 Shopline 商店中永久刪除指定評論,適用於移除違規、惡意或測試用評論。

【呼叫的 Shopline API】

  • DELETE /v1/product_review_comments/{comment_id}

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

【副作用】

  • 永久刪除評論記錄,不可復原

  • 商品的評論總數與平均評分將同步更新

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYes評論 ID
Behavior5/5

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

Without annotations, the description fully discloses permanent deletion, irreversibility, and automatic update of product review count and average rating. No contradictions.

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?

The description is well-structured with sections for purpose, usage, API call, return structure, and side effects. It is front-loaded and concise, though slightly repetitive in some parts.

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?

The description covers all necessary aspects: action, use cases, API endpoint, return structure, and side effects. No output schema exists, but the return format is described. It is complete for a single-parameter delete tool.

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?

The schema already provides 100% coverage with a clear description of the 'comment_id' parameter. The description adds no new semantic information 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 clearly states the tool deletes a single product review, specifies its use for removing violative, malicious, or test reviews, and distinguishes from bulk delete tools. The verb 'delete' and resource 'product review' are explicit.

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?

The description provides clear use cases (removing violative, malicious, or test reviews) and implicitly contrasts with bulk delete by specifying single review. However, it does not explicitly exclude other scenarios or mention prerequisites.

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