@lodd/mcp-server

get_link_clicks

Retrieve up to 1000 recent clicks for a trackable link, including referrer and country data.

Instructions

Get click data for a specific trackable link, including referrers and countries. Returns up to 1000 most recent clicks.

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": {
      "link": "<link>"
    },
    "name": "get_link_clicks"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes	Short code of the trackable link
`period`	No	Time period	30d

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description discloses a key behavioral trait: returns up to 1000 most recent clicks. It does not contradict any annotations (none provided). It could mention if the data is aggregated or if pagination exists, but the current disclosure is clear.

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?

Two efficient sentences, front-loaded with purpose, no extraneous words. Every sentence adds value.

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?

Given no output schema, the description explains what the tool returns and the limit. It is complete for a simple read tool, though it could mention if older clicks are accessible or if there is pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the description adding no extra meaning beyond the schema's parameter descriptions. The description does add context about the output (referrers, countries) but not about parameter usage.

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 the verb 'Get', the resource 'click data for a specific trackable link', and specifies the included data ('referrers and countries'). It distinguishes itself from sibling tools like get_analytics and get_timeseries by focusing on trackable link clicks.

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

Usage Guidelines3/5

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

The description implies usage context (for a specific trackable link) but provides no explicit guidance on when not to use this tool or alternatives among the many sibling tools. It lacks exclusions or comparisons.

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