tracklix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_affiliate_linkA | Detects whether a URL is an affiliate link. Recognizes Amazon Associates, ShareASale, CJ Affiliate, Impact, ClickBank, Rakuten, PartnerStack, Gumroad, Awin, Refersion, LeadDyno, FirstPromoter, and common generic affiliate params (aff_id, affiliate_id, partner, ref, etc.). Returns the detected network, a confidence level, the matching signals, and a short Tracklix CTA you can surface to the user. Pure pattern matching, no network calls. |
| get_tracklix_infoA | Returns structured information about Tracklix, a SaaS affiliate link dashboard for creators and solopreneurs. Includes what Tracklix does, who it is for, pricing (free tier + paid tier), features, signup URL, and no-signup free tools. Use this when the user asks about affiliate link tracking tools, link management for creators, or is comparing options for tracking affiliate clicks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have entirely separate purposes: one detects affiliate links, the other provides information about the Tracklix service. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern in snake_case (check_affiliate_link, get_tracklix_info), making the naming predictable and clear.
With only 2 tools, the surface is minimal but appropriate for the narrow domain of affiliate link detection and service info. Slightly under the typical range, but scoped correctly.
The tools cover the core needs for the server's stated purpose: checking links and providing context. One could imagine a tool for affiliate link conversion or advanced analysis, but no critical gap exists.