Skip to main content
Glama
Sign In

Reeltopus

by com.reeltopus
OverviewDiscussionsAdmin

Get smart link stats

get_link_stats
Read-onlyIdempotent

How the tracked short links in the user's posts are doing over the last days days (default 30): clicks by people (bots and link previews left out), unique clicks, click-through (unique clicks ÷ views, where the platform reports views), leads and sales the user's site reported, per link, per platform and per clip, plus the best-converting clips. clipId narrows it to one clip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_link_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to count (1-365, default 30).
clipIdNoOnly this clip's links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on semantics: it discloses that bot and link-preview clicks are filtered out, how click-through is computed (unique clicks ÷ views, only where the platform reports views), and that leads/sales come from the user's own site reporting. This is meaningful context an agent could not infer from the annotations.

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 purpose is front-loaded, and the long metric enumeration is dense but each clause carries real information. A tighter split into two sentences would improve scanability, but nothing is filler.

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?

With no output schema, the description does the necessary work of describing return content (metric types plus per-link/per-platform/per-clip breakdowns and best-converting clips). Only minor gaps remain, such as whether empty results or missing view data appear as nulls.

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 the schema already documents both parameters including the 30-day default and the 1-365 range. The description restates the default and clip scoping but adds no syntax or edge-case detail beyond the schema.

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 states a specific resource (tracked short links in the user's posts) and enumerates the exact metrics returned: clicks excluding bots/previews, unique clicks, click-through ratio, leads and sales, broken down per link, platform and clip. It is clearly distinct from report-oriented siblings like get_packaging_report and get_sponsor_report.

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?

Usage is implied by the data it returns, and the closing sentence explains that clipId narrows the result to one clip. However, there is no explicit when-to-use guidance, no exclusion (e.g., when to use a different report tool), and no stated prerequisites.

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

All Reeltopus toolsInspect
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.

Resources