Get view analytics for one of the user's own KooLink short links: total and valid (fraud-filtered) views, breakdowns by device, country and referrer, plus a trailing 7-day trend. Use this to answer 'how is my link performing'.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The short code (the part after kool.ink/). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It adds useful behavioral context: the link must be the user's own, and views are fraud-filtered. However, it does not disclose authentication requirements, error behavior for invalid codes, or whether the operation requires any special permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and information-dense: purpose, scope, included metrics, and the intended user question are all covered in two sentences. Key facts are front-loaded and no words are wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-param, read-only analytics tool without an output schema, the description adequately explains what data will be returned and what the param means. It could be more complete by noting what happens for invalid/unknown codes or if authorization is required, but those are secondary for selecting and invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents 'code' as the short code. The description adds practical meaning beyond the schema by specifying 'the part after kool.ink/', making the expected value format concrete and unambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the specific verb 'Get view analytics' and the resource (the user's own KooLink short links). Names the concrete data returned: total/valid views, device/country/referrer breakdowns, and a 7-day trend, which clearly distinguishes it from the sibling tools list_links and shorten_url.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides an explicit use case: 'Use this to answer how is my link performing.' This gives clear context for when to invoke. It does not explicitly name alternatives or exclusions, but the intended scenario is obvious against the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a clearly distinct purpose: creating a short link, listing links, and fetching stats for a specific link. There is no overlap or ambiguity between them.
Tool names follow a consistent verb_noun pattern: shorten_url, list_links, link_stats. All are lower_snake_case and uniformly readable.
Three tools is a reasonable, focused scope for a URL shortener server. It is slightly minimal but each tool covers a core need without unnecessary bloat.
The core URL shortening workflow is covered: create, list, and analyze performance. Missing update/delete capabilities are minor gaps since users can still manage links through the KooLink UI, but the tool surface has no obvious dead ends for its primary purpose.