Split (creator affiliate platform)

Click a SplitLink

split_click_link

Resolve a SplitLink you RECEIVED — from another agent, a creator, a message — into its tracked destination, registering the click as this account. Use this instead of navigating to the SplitLink: the sender keeps their attribution, this account is recorded as the shopper (and receives the buyer share where the merchant offers one), and you get structured facts BEFORE deciding to navigate: destination_domain, target_url, the commission rate, whether the link is this account's own, and disclosure flags for anything you show a person. tracked_url is what to open to buy — unchanged; requires_redirect true means it is an affiliate network's one-hop redirector (follow it, keep cookies), false means the store URL with Split's parameter. Split establishes attribution only; it does not decide whether to buy — that stays with the person or their commerce system. Never re-monetize a received SplitLink's destination with your own link: resolve the link you were given. Each call registers a click, so call it per purchase intent, not per impression. as: anonymous clicks as an unknown shopper (no buyer share, the creator earns all), optionally carrying your own shopper id.

Input Schema

TableJSON Schema

Name	Required	Description
`as`	No	me (default): this account is the shopper. anonymous: an unknown shopper
`split_link`	Yes	The SplitLink as received: https://spl.it/<code> (a shop_it_url carrying auth_token works too), or a bare short code
`anonymous_id`	No	With as: anonymous — a stable shopper id from your system; its last 11 characters are stamped into the click id

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate readOnly=false and idempotent=false; the description confirms side effects ('Each call registers a click') and details attribution behavior, anonymous mode, and redirect handling. No contradiction with annotations.

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?

The description is long (~150 words) but dense, front-loading the purpose and covering usage, behavior, and parameters. Each sentence adds value without redundancy, though it could be slightly tightened.

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?

Given no output schema, the description lists key return fields (destination_domain, target_url, commission rate, own-link flag, disclosure flags) and explains tracked_url and requires_redirect. It also covers side effects and usage context, making it complete for the tool's complexity.

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%, so baseline is 3, but the description adds meaningful context: it explains the 'as' parameter's implications (anonymous: no buyer share, creator earns all) and mentions optional shopper id, going 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 states a specific action: resolve a received SplitLink into its tracked destination and register a click. It clearly distinguishes from creating or monetizing links by saying 'Never re-monetize a received SplitLink's destination with your own link: resolve the link you were given.'

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

Usage Guidelines5/5

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

Explicitly instructs 'Use this instead of navigating to the SplitLink' and 'call it per purchase intent, not per impression.' It also implies when not to use other tools by warning against re-monetizing the destination.

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

All Split (creator affiliate platform) 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?