Snipzr

Get link statistics

snipzr_get_link_stats

Read-only

Per-day clicks and scans for one link, with bots, AI assistants and suspected automated traffic counted separately, each with its reasons: a link's performance.

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": "snipzr_get_link_stats"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	the link's back-half
`zoneDomain`	No	the link's short domain exactly as it appears in the link's short URL (lowercase, no scheme); omit for links on the default domain
`workspaceId`	No	act in this granted workspace (user tokens carrying a grant for it); omit for the token's own space

Output Schema

Name	Required	Description	Default
`stats`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedOutput schema / properties / stats / properties / allTime / properties / imported

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "importedAt": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "source",
+    "importedAt"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

Changed8 schema fields changedOct 8, 2026

addedOutput schema / properties / stats / properties / notHuman

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "aiAssistants": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "k": {
+            "type": "string"
+          },
+          "v": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "k",
+          "v"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "botsAndPreviews": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "k": {
+            "type": "string"
+          },
+          "v": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "k",
+          "v"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "suspected": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "k": {
+            "type": "string"
+          },
+          "v": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "k",
+          "v"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "botsAndPreviews",
+    "aiAssistants",
+    "suspected"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / stats / properties / series / items / properties / ba
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / stats / properties / series / items / properties / bs
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / stats / properties / totals / properties / aiAssistants
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / stats / properties / totals / properties / botsAndPreviews
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / stats / properties / totals / properties / suspected
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / stats / properties / totals / required

Previous value: -[
-  "human",
-  "bots",
-  "requests",
-  "qr",
-  "click"
-]New value: +[
+  "human",
+  "bots",
+  "requests",
+  "qr",
+  "click",
+  "botsAndPreviews",
+  "aiAssistants",
+  "suspected"
+]

changedOutput schema / properties / stats / required

Previous value: -[
-  "slug",
-  "zoneDomain",
-  "range",
-  "allTime",
-  "totals",
-  "series",
-  "hourly",
-  "geo",
-  "referrers",
-  "devices",
-  "browsers",
-  "os",
-  "languages",
-  "source",
-  "freshness"
-]New value: +[
+  "slug",
+  "zoneDomain",
+  "range",
+  "allTime",
+  "totals",
+  "series",
+  "hourly",
+  "geo",
+  "referrers",
+  "devices",
+  "browsers",
+  "os",
+  "languages",
+  "source",
+  "notHuman",
+  "freshness"
+]

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / zoneDomain / description

Previous value: -"the link's short domain EXACTLY as snipzr_list_domains reports it; omit for links on the default domain"New value: +"the link's short domain exactly as it appears in the link's short URL (lowercase, no scheme); omit for links on the default domain"

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing that bots, AI assistants and suspected automated traffic are counted separately with reasons, which is behavioral context the annotations do not carry; however, it says nothing about auth requirements or the time window being reported.

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?

It is a single compact sentence with the core return content front-loaded ('Per-day clicks and scans for one link'). The trailing fragment 'a link's performance' is redundant restatement and slightly muddies the sentence but costs little.

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 the description need not enumerate return fields, and it correctly summarizes the segmentation of traffic types. The notable gap is that no reporting period or date-range behavior is described despite the 'per-day' framing, leaving the agent unsure what window the statistics cover.

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 100%, so slug, zoneDomain and workspaceId are fully documented in the schema itself, establishing the baseline of 3. The description adds no syntax or format detail beyond 'for one link', so it does not compensate with extra meaning.

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 specifies the verb+resource ('clicks and scans for one link') and even the granularity ('per-day'), so an agent knows this returns time-series metrics rather than link metadata. It does not explicitly differentiate itself from siblings like snipzr_get_link or snipzr_get_campaign_report, but the resource is specific enough to be distinguishable.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The phrase 'for one link' weakly implies single-link scope versus an aggregate report, but nothing routes the agent toward or away from the campaign report or get_link tools.

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

All Snipzr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.