AWSYS Links

Create Affiliate Program

create_affiliate_program

Create a new affiliate program. You become the merchant and can approve partners who join. Requires Builder tier or higher. Supports CPC (cost-per-click), CPA return-visit tracking, or both. Partners promote your links and earn commissions you define; awsys.co handles tracking only — payments are made directly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "commission_type": "<commission_type>"
    },
    "name": "create_affiliate_program"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Program name (3–100 characters)
`cpa_rate`	No	Cost-per-acquisition rate in USD (0.01–1000.00). Required when commission_type is "cpa_return" or "both".
`cpc_rate`	No	Cost-per-click rate in USD (0.01–10.00). Required when commission_type is "cpc" or "both".
`is_public`	No	Whether the program appears in the public discovery listing (default true)
`description`	No	Public description of the program (max 500 characters)
`commission_type`	Yes	Commission model: cpc (per unique click), cpa_return (per return visit/conversion), or both
`cookie_duration_days`	No	How many days the affiliate tracking cookie lasts (1–365, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (which only declare write, non-idempotent, non-destructive), the description adds real operational context: tier gating, the merchant/approver role, and the important caveat that awsys.co handles tracking only and payments settle directly. It does not describe failure modes or what happens to program state afterward, so it stops short of a 5.

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?

Purpose and role are front-loaded in the first sentence, followed by the tier gate and the commission mechanics. The partner-promotion clause is mildly promotional but still carries the commissions-are-merchant-defined meaning, so little is truly wasted.

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 7-parameter mutation with no output schema and fully documented params, the description covers eligibility, commission models, and the payment-boundary caveat. It omits defaults and any note on created-program retrieval (e.g., get_affiliate_program) which would round it out.

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?

Schema coverage is 100%, and the schema already explains cpc vs cpa_return vs both with ranges and conditionality, so the schema does the heavy lifting. The description adds only the framing that partners earn commissions the merchant defines and that both models can be combined, which is marginal over the enum documentation. Baseline 3 applies.

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?

The description opens with a specific verb+resource ("Create a new affiliate program") and clarifies the caller's role as merchant with partner-approval authority. That is enough to separate it from update_affiliate_program and join_affiliate_program, though no sibling is named explicitly.

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?

It supplies a concrete prerequisite ("Requires Builder tier or higher"), which tells an agent when the call is even permitted. It gives no explicit exclusions or pointers to alternatives such as join_affiliate_program or update_affiliate_program, so it stays at clear-context rather than full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AWSYS Links tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?