Skip to main content
Glama

update_flash_price_campaign

Update a flash sale campaign's price, schedule, or eligible products to modify live promotions. Changes take effect immediately.

Instructions

[WRITE] 更新快閃價格活動。

【用途】 修改已建立的快閃價格活動,例如調整特價金額、活動時段或適用商品範圍。

【呼叫的 Shopline API】

  • PUT /v1/flash_price_campaigns/{campaign_id}

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

【副作用】

  • 修改立即生效;若活動正在進行中,前台價格即時更新

  • 不可復原(無版本歷史),但可再次呼叫此工具覆蓋

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes快閃價格活動 ID
campaign_dataYes要更新的活動欄位(僅傳入需修改的欄位)
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: immediate effect on active campaigns, irreversibility (無版本歷史), and the API endpoint. This meets the transparency burden comprehensively.

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?

The description is highly structured with clear sections (用途, API, 回傳結構, 副作用), each sentence adding unique value. No redundancy.

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 2-parameter tool with no output schema or annotations, the description covers API endpoint, return structure, and side effects. Missing error handling or permission details, but sufficient for the complexity.

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 coverage is 100% with descriptions for both parameters. The description adds the nuance that campaign_data should only include fields to modify (partial update), which goes 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 it updates a flash price campaign (修改已建立的快閃價格活動). The [WRITE] prefix and sibling tools (create_flash_price_campaign, delete_flash_price_campaign, etc.) distinguish it effectively.

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 用途 section provides concrete examples (adjusting price, time period, product scope) and implies usage context. It does not explicitly exclude scenarios or mention alternatives, but the purpose 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