Skip to main content
Glama

get_product_subscription_detail

Retrieve complete details of a product subscription, including customer info, payment, shipping, and billing cycle. Use to confirm subscription status in customer service.

Instructions

取得單一商品訂閱的完整詳情。

【用途】 查詢特定訂閱紀錄的完整資訊,包含客戶、商品、付款方式、配送設定與 訂閱週期等所有欄位。適合客服場景或個別訂閱狀態確認。

【呼叫的 Shopline API】

  • GET /v1/product_subscriptions/{subscription_id}

【回傳結構】 dict 包含 id, customer_id, product_id, variant_id, status, frequency, frequency_unit, price (TWD), shipping_address, payment_method, next_billing_at, created_at, updated_at 等完整欄位。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idYes商品訂閱 ID(由 list_product_subscriptions 回傳的 id 欄位)
Behavior4/5

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

No annotations provided, but description describes return structure comprehensively. It implies a read-only query operation, but does not explicitly state lack of side effects or permissions required.

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 for purpose, API call, and return fields. Every sentence is informative, and the format is clean and easy to parse.

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?

Given the tool has one parameter and no output schema, the description covers purpose, API endpoint, return structure, and use case. It is complete and self-contained.

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 has 100% coverage with a clear description linking subscription_id to the id field from list_product_subscriptions. Description mentions the parameter but adds marginal extra value.

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?

Description clearly states it retrieves complete details of a single product subscription, with specific fields listed. It distinguishes from sibling tools like list_product_subscriptions by focusing on a single record and providing full detail.

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?

States use case is for customer service scenarios or individual subscription confirmation. Implicitly differentiates from listing tool but does not explicitly mention alternatives 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