Skip to main content
Glama

get_order_action_logs

Retrieve complete history of order operations including status changes, operator details, and timestamps for audit and tracking purposes.

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)
Behavior3/5

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

No annotations were provided, so the description carries the full burden. It implies a read operation (GET API, retrieving history) but does not explicitly state side effects, rate limits, pagination, or error conditions. The return structure is given, but behavioral guarantees are lacking.

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 clear sections (purpose, API, return structure). It is front-loaded and efficient, though the inclusion of a full JSON example adds length but aids understanding. Every sentence contributes meaning.

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?

For a simple read-only tool with one parameter and no output schema, the description covers purpose, parameter source, and return format adequately. It lacks error handling or edge cases, but these are acceptable for this complexity level.

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

Parameters5/5

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

The schema covers 100% of parameters, and the description adds crucial context: the order_id is the internal ID from query_orders, not the order_number. This prevents misuse and clarifies data source, adding significant value 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 retrieves all operation history for a specified order, including status changes, personnel, timestamps, and is suitable for audit trails. This specific verb-resource combination distinguishes it from siblings 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 Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. While the description mentions suitability for audit trails, it does not exclude other uses or compare with other order-related tools. Missing context like prerequisites (e.g., order must exist) or when not to use.

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