Skip to main content
Glama

create_affiliate_campaign

Create an affiliate campaign to set reward rules for partners, enabling commission tracking on orders generated through referral links or codes.

Instructions

[WRITE] 建立聯盟行銷活動。

【用途】 建立聯盟行銷(Affiliate)活動,設定推薦獎勵規則,讓推廣夥伴(聯盟會員) 透過分享連結或代碼帶來訂單並獲得佣金。

【呼叫的 Shopline API】

  • POST /v1/affiliate_campaigns

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

【副作用】

  • 活動建立後,可將活動連結或代碼分發給聯盟夥伴

  • 活動啟用後,透過聯盟連結產生的訂單將自動計算佣金

  • 請確認佣金規則與結算方式設定正確,避免財務損失

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_dataYes聯盟行銷活動資料(參考 Shopline affiliate_campaign 物件結構)
Behavior4/5

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

No annotations provided, so the description carries full burden. It lists side effects such as commission calculation and financial risks, adding transparency beyond the basic write operation.

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 clear sections and front-loaded purpose. Each section is concise and informative, though some redundancy exists (e.g., API endpoint in multiple places).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers creation context and side effects, but lacks details on required fields within campaign_data and does not explain the return structge thoroughly. Missing output schema increases need, but description partially addresses it.

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_data) with 100% schema coverage. The schema description is vague, and the tool description does not add meaningful detail about the object structure, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it creates an affiliate campaign with reward rules, distinguishing it from siblings like update or delete. However, it does not explicitly contrast with update or other creation tools.

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?

Includes a usage section explaining when to use the tool for setting up affiliate campaigns, but lacks explicit when-not-to-use or alternative tool references.

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