affiliate-networks-mcp

affiliate_addrevenue_generate_tracking_link

Generate an Addrevenue tracking link for a given programme and destination URL, enabling affiliate sharing of specific product or page links.

Instructions

Generate a tracking link on Addrevenue for a given programme and destination URL. Use this when the user wants to share an affiliate link to a specific product or page on a merchant they have joined. Returns a TrackingLink; pair with list_programmes to confirm the programmeId before calling.

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": {
      "programmeId": "<programmeId>",
      "destinationUrl": "<destinationUrl>"
    },
    "name": "affiliate_addrevenue_generate_tracking_link"
  }
}

Input Schema

Name	Required	Description	Default
`programmeId`	Yes
`destinationUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.20.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior3/5

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

There are no annotations, so the description carries the full burden. It discloses that a TrackingLink is returned, but does not mention any side effects, authentication requirements, rate limits, or error conditions. For a simple link generator this is adequate but not comprehensive.

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 three concise sentences: a clear action, a usage context, and a return/prerequisite note. Every sentence adds value with no repetition or wasted words.

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 tool with only two string parameters and no output schema, the description covers the core aspects: what it does, when to use it, what it returns, and a prerequisite. It does not cover potential errors or parameter formats, but the tool is simple enough that these gaps are minor.

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?

The schema has no descriptions, but the description clarifies both parameters: 'programme' for programmeId and 'destination URL' for destinationUrl, and adds the tip to use list_programmes to confirm the programmeId. This compensates for the 0% schema coverage, though it doesn't specify URL format constraints.

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 'Generate a tracking link on Addrevenue for a given programme and destination URL,' specifying the exact verb, resource, and network. This distinguishes it from other network-specific generate_tracking_link tools and from addrevenue's list/get 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?

It explicitly says to use this when the user wants to share an affiliate link to a specific product or page. It also advises pairing with list_programmes to confirm the programmeId, providing clear contextual guidance, though it does not mention when not to use it or name alternative tools.

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

Deploy Server