ATTIM

Get link stats

get_link_stats

Read-onlyIdempotent

Views, clicks, and click-through rate for each link and project on a profile or link page, and why each Smart link is where it is. Free plans see 7 or 30 days.

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": {
      "slug": "<slug>"
    },
    "name": "get_link_stats"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`slug`	Yes

Output Schema

Name	Required	Description	Default
`slug`	Yes
`links`	Yes
`range`	Yes
`projects`	No
`pageViews`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / slug / minLength
```
Removed value: -1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "links": {
+      "items": {
+        "properties": {
+          "clicks": {
+            "type": "integer"
+          },
+          "ctr": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "uniqueClicks": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pageViews": {
+      "type": "integer"
+    },
+    "projects": {
+      "items": {
+        "properties": {
+          "clicks": {
+            "type": "integer"
+          },
+          "ctr": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "uniqueClicks": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "range": {
+      "properties": {
+        "days": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "range",
+    "pageViews",
+    "links"
+  ],
+  "type": "object"
+}

First observedNov 10, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive closed-world behavior, so the safety profile is covered. The description adds a genuinely non-structured behavioral fact: visibility is capped by plan tier (7 or 30 days for free plans), which affects interpretation of results. It does not mention pagination or defaults, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and contains no filler, but it is structured as one long clause plus a fragment, and the phrasing 'why each Smart link is where it is' is vague where a concrete term like routing rationale would be. The plan-limit sentence is tacked on without a connector.

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?

An output schema exists, so return values need no explanation, and the tool is simple with only two parameters. However, the ambiguity around the days parameter and the plan-based window, plus no guidance relative to the analytics sibling, leaves an agent with open questions about correct invocation.

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 description coverage is 0%, so the description must carry parameter meaning, and it only partially does: 'on a profile or link page' hints that slug may identify either a profile or a link page. The days parameter (1-365 in schema) is never explained, and 'Free plans see 7 or 30 days' ambiguously mixes plan limits with the days input rather than clarifying it.

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 names specific metrics (views, clicks, click-through rate) and the scope (each link and project on a profile or link page), plus the Smart link routing rationale. It does not distinguish itself from the sibling get_insights, so an agent cannot tell which analytics tool to pick from the description alone.

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?

There is no statement of when to use this versus get_insights or get_profile, and no prerequisites or exclusions. The only context offered is a plan-tier data window ('Free plans see 7 or 30 days'), which is a constraint rather than usage guidance.

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

All ATTIM tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?