@lodd/mcp-server

list_trackable_links

Retrieve all trackable links for a site along with click statistics. Filter by active, archived, or all statuses.

Instructions

List all trackable links for a site with their click statistics

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": {
      "site": "<site>"
    },
    "name": "list_trackable_links"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Site domain or UUID
`status`	No	Filter by status	active

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations exist, so the description must carry full burden. It discloses that it lists all trackable links with click statistics, implying a read operation. However, it does not mention default filter behavior (e.g., 'active' links as per schema default) or pagination.

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 a single, concise sentence that communicates the core functionality. It is efficient but lacks any structure (e.g., bullet points for parameters or output).

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?

Given the absence of an output schema and annotations, the description provides the essential purpose. However, it omits details like default filters (active status) and whether results are paginated. For a tool with 2 parameters, this is acceptable but not thorough.

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?

The input schema has 100% coverage, so the description adds no extra meaning beyond the schema. It does not elaborate on parameter values or provide examples. Baseline 3 is appropriate.

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 clearly states the verb 'list' and the resource 'trackable links for a site', and specifies that it returns 'click statistics'. This is specific and informative, but it does not distinguish from the sibling tool 'get_link_clicks' which might retrieve clicks for a single link.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_link_clicks'. There is no mention of prerequisites, filtering options, or context for use.

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