Skip to main content
Glama

delete_affiliate_campaign

Delete an affiliate campaign permanently to remove ended, cancelled, or erroneous campaigns. Referral links become invalid; historical commission data remains.

Instructions

[WRITE] 刪除聯盟行銷活動。

【用途】 永久刪除指定的聯盟行銷活動。用於清除已結束、取消或錯誤建立的活動。

【呼叫的 Shopline API】

  • DELETE /v1/affiliate_campaigns/{campaign_id}

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

【副作用】

  • 永久刪除該活動,不可復原

  • 刪除後聯盟夥伴的推廣連結或代碼將失效,無法再追蹤新訂單

  • 已累積的佣金紀錄與歷史訂單資料不受影響(依 Shopline 實作而定)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes聯盟行銷活動 ID
Behavior5/5

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

No annotations provided, so description carries full burden. It includes a '副作用' section detailing permanent deletion, irreversibility, and effects on affiliate links. This adequately discloses behavioral traits beyond the input schema.

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?

Well-structured with sections for operation type, usage, API, response, and side effects. Information is front-loaded. Could be slightly more concise, but adds useful context like return structure and API endpoint.

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 is a simple delete with one parameter, the description covers purpose, usage guidelines, side effects, API endpoint, and return structure. No output schema, but description compensates by listing return fields. Sibling tools provide context.

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?

Only one parameter (campaign_id) with 100% schema coverage. Description does not add meaning beyond the schema; it only includes the endpoint. Baseline score of 3 is appropriate as schema already documents the parameter.

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 '永久刪除指定的聯盟行銷活動' (permanently delete specified affiliate campaign), which is a specific verb+resource. It starts with '[WRITE]' and is distinct from sibling tools like create_affiliate_campaign, update_affiliate_campaign, get_affiliate_campaign_detail, etc.

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 explains when to use the tool: '用於清除已結束、取消或錯誤建立的活動' (for clearing finished, cancelled, or incorrectly created campaigns). This provides clear context, though it does not explicitly state when not to use or mention alternatives.

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