AWSYS Links

Join Affiliate Program

join_affiliate_program

Apply to join another merchant's affiliate program as a partner. Your application starts in "pending" status until the merchant approves it. A unique partner tracking code is auto-generated (or you can supply a custom one).

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": {
      "program_id": "<program_id>"
    },
    "name": "join_affiliate_program"
  }
}

Input Schema

Name	Required	Description	Default
`program_id`	Yes	The program ID to join
`partner_code`	No	Optional custom partner code (4–12 alphanumeric chars). Auto-generated if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior. The description adds real context beyond them: the application lands in a 'pending' state pending merchant approval, and a tracking code is auto-generated or user-supplied. It stops short of stating what happens on a duplicate application or how approval is surfaced.

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?

Three short sentences, front-loaded with the core action and followed by the state and code-generation details. Minor redundancy with the schema on the auto-generated code, but nothing is wasted.

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?

For a two-parameter mutation with full schema coverage, annotations, and no output schema, the description supplies the key lifecycle fact (pending approval) an agent needs to set expectations. No significant gap remains for calling it correctly.

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 description coverage is 100%, so both parameters are already documented, including the 4–12 alphanumeric constraint and the auto-generation fallback. The description only restates the auto-generation behavior, adding no new meaning 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 uses a specific verb ('apply to join') plus resource ('another merchant's affiliate program as a partner'), which also disambiguates it from siblings like create_affiliate_program (own program) and leave_affiliate_program. An agent can pick this tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intent is implied by 'apply to join another merchant's affiliate program,' but there is no explicit when-to-use/when-not guidance. Nothing tells the agent whether to check get_affiliate_limits or list_affiliate_partnerships first, or how to handle a program the agent already belongs to.

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?