Skip to main content
Glama
tzangms

shopline-mcp

by tzangms

get_order_action_logs

Retrieve complete action logs for a specific order, including status changes, operators, and timestamps, to support audit tracking and troubleshooting.

Instructions

【用途】取得指定訂單的所有操作歷程紀錄,包含狀態變更、人員操作、時間戳記等,適合稽核追蹤。

【呼叫的 Shopline API】

  • GET /v1/orders/{order_id}/action_logs

【回傳結構】 { "order_id": str, # 查詢的訂單 ID "total": int, # 歷程總筆數 "logs": [ # 操作歷程列表 { "action": str, # 操作類型(如 status_changed, payment_updated) "operator": str, # 操作人員 "created_at": str, # 操作時間 ... # 其他欄位依 API 回應而定 } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes訂單內部 ID(由 query_orders 回傳的 id 欄位,非 order_number)
Behavior4/5

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

With no annotations, the description carries the full burden of disclosure. It includes the underlying API endpoint, response structure, and field meanings, giving clarity about the read-only nature and output. It lacks details on pagination, error handling, or rate limits, but the provided specifics are substantial.

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 labeled sections (purpose, API call, response structure), front-loading the purpose. It is slightly longer due to the output example, but every section adds value and there is no redundant information.

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?

The tool has a single parameter, and the description provides a sample response with key fields, making the tool's behavior understandable. While no output schema exists, the provided structure fills that gap. The absence of explicit alternative comparisons is a minor omission, but overall the description is complete for a simple read-only 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 input schema already provides 100% coverage with a clear description of order_id as the internal ID from query_orders, not order_number. The description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 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?

The description clearly states the tool retrieves all operation history logs for a specified order, including status changes, operator actions, and timestamps. This specific verb+resource combination distinguishes it from sibling tools like get_order_detail or get_order_transactions.

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 mentions it is suitable for audit tracking, providing clear context for when to use it. However, it does not explicitly name alternatives or state when not to use it, falling short of a complete usage guide.

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/tzangms/shoplinemcp'

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