LinkPulse
Server Details
Know what every affiliate link actually earns, and fix what's bleeding revenue.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 5 of 5 tools scored.
Each tool has a distinct purpose: at_risk_articles combines broken links with revenue loss, broken_links lists all broken links, revenue_summary gives revenue data, suggest_replacement finds alternatives, and top_articles shows top earners. There is no overlap.
All tool names follow a consistent snake_case pattern with descriptive terms like adjective_noun (at_risk_articles, broken_links) or verb_noun (suggest_replacement). No mixing of conventions.
5 tools is well-scoped for a server focused on affiliate link management and revenue optimization. Each tool serves a clear purpose without redundancy.
The set covers finding broken links, assessing revenue impact, and suggesting replacements, but lacks an 'apply_fix' tool to actually implement changes, which is mentioned as v1.1. Missing update/delete functionality for links.
Available Tools
5 toolsat_risk_articlesArticles at risk (revenue × broken-link cross-join)Inspect
Articles that are earning affiliate commissions AND have broken affiliate links on the page — the revenue currently leaking each month. This is the cross-join between WeCanTrack revenue data and LinkPulse's local link scanner. Returns empty if the site has no broken links on earning articles. Use this to answer "where am I losing money" and prioritize fixes.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Revenue window in days (default 30). |
broken_linksBroken affiliate linksInspect
All broken affiliate links currently flagged by the LinkPulse scanner on this site. Status 4xx (dead) and 3xx (redirecting) are both included, grouped by post. Useful for audit-style questions and for piping into suggest_replacement.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
revenue_summaryRevenue summaryInspect
Total affiliate commissions for the current site over a window (default 30 days), with transaction count, average commission, and delta vs. the equivalent prior window. Data comes from WeCanTrack via the LinkPulse sync pipeline.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Window size in days (1-365, default 30). |
suggest_replacementSuggest an alternative affiliate product URLInspect
Given a broken or dead affiliate URL plus the article it sits on, ask Claude (with web search) to find the closest-available alternative product on the same retailer or network. Returns a candidate URL, short reasoning, confidence, and a URL-reachability check. This is the "autonomous fix suggestion" that makes LinkPulse agent-native — the v1.1 apply_fix tool will consume this output directly.
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | Affiliate network (e.g. Awin, Bol.com, Daisycon) if known. | |
| broken_url | Yes | The affiliate URL that is dead or redirecting. | |
| anchor_text | No | The visible anchor text of the broken link, if known. | |
| article_title | No | Title of the article the link appears on (helps with context). |
top_articlesTop earning articlesInspect
Articles on the current site that generated the most commission over a window. URL grouping strips tracking parameters so the same article with different ?gclid= values is counted together. Use this to answer "which posts make money" and "where should I spend editorial time".
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Window size in days (default 30). | |
| limit | No | Max articles to return (default 10). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!