Affilio Link Tools

Auth.Add Product Link

auth.add_product_link

Associate an affiliate link with a product in your Affilio catalog.

This is how you connect an affiliate URL to a product so it appears in storefront listings and can be tracked per-product. A single product can have multiple links — one per country, platform, or affiliate network.

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": {
      "product_id": "<product_id>",
      "link_id": "<link_id>"
    },
    "name": "auth.add_product_link"
  }
}

Input Schema

Name	Required	Description	Default
`link_id`	Yes	Link ID returned by auth.create_link.
`product_id`	Yes	Product ID returned by auth.create_product or auth.get_product.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 9, 2026

changedInput schema / properties / link_id / description

Previous value: -"Unique link/URL ID (MongoDB ObjectId string) of the affiliate link to associate with this product. Create links first via auth.create_link, then pass the returned ID here."New value: +"Link ID returned by auth.create_link."

changedInput schema / properties / product_id / description

Previous value: -"Unique product ID (MongoDB ObjectId string) of the product to attach the link to. Retrieve via auth.create_product or auth.get_product."New value: +"Product ID returned by auth.create_product or auth.get_product."

Changed2 schema fields changedJun 26, 2026

addedInput schema / properties / link_id / description

Added value: +"Unique link/URL ID (MongoDB ObjectId string) of the affiliate link to associate with this product. Create links first via auth.create_link, then pass the returned ID here."

addedInput schema / properties / product_id / description

Added value: +"Unique product ID (MongoDB ObjectId string) of the product to attach the link to. Retrieve via auth.create_product or auth.get_product."

AddedJun 25, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It does disclose the consequence of the call (link appears in storefront listings, trackable per-product), which is useful, but says nothing about idempotency, whether re-linking the same pair duplicates, ownership/permission requirements, or what happens if the link is already associated elsewhere.

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?

Three short sentences, front-loaded with the core action and followed by the effect and the multiplicity rule. No filler and nothing redundant with the schema.

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?

An output schema exists, so return values needn't be explained, and the parameter side is fully covered. However, for an unannotated mutation tool the description leaves meaningful gaps around permissions, overwrite/duplicate behavior, and failure modes, which is only borderline complete.

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?

Schema coverage is 100% and both IDs are explained there, so baseline is 3. The description adds genuine semantic value beyond the schema by stating the multiplicity model — a product can hold multiple links, one per country, platform, or affiliate network — which tells the agent this is a many-to-many association rather than a replacement.

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 gives a specific verb+resource pair ("Associate an affiliate link with a product") and scopes it to the Affilio catalog, which clearly distinguishes it from create_link or update_link. It stops short of naming a sibling it is not, so it lands at 4 rather than 5.

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 clear situational context: this is how you make an affiliate URL appear in storefront listings and be tracked per-product. There is no explicit "when not to use" or routing to alternatives such as auth.create_link, but the usage trigger is unambiguous.

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

All Affilio Link Tools 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?