Skip to main content
Glama
Sign In

URLinks

by me.urlinks
OverviewDiscussionsAdmin

get_link_analytics

Read-only

Get click analytics for a shortlink — total clicks, daily breakdown, and last clicked time.

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": {
      "shortlink": "<shortlink>"
    },
    "name": "get_link_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days of history (default 30, max 90)
shortlinkYesThe shortlink to get analytics for (e.g., 'my/docs')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already establishes this as a safe read. Beyond that, the description discloses the shape of the result — total clicks, daily breakdown, last clicked time — which is genuinely useful because no output schema exists. It omits timezone/bucketing semantics and behavior for links with zero clicks, 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.

Conciseness5/5

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

A single sentence with the resource and the returned metrics front-loaded; there is no redundant restatement of the name and no 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?

For a two-parameter read-only tool with full schema coverage, the description covers purpose and return contents adequately. Minor gaps remain around aggregation semantics (timezone, whether the daily breakdown respects the `days` window) but nothing blocking for 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 100%, and the schema already documents the `days` default of 30 and maximum of 90 as well as the shortlink format. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 states a specific verb+resource ("Get click analytics for a shortlink") and enumerates the returned metrics, which separates it from the profile-level sibling get_profile_analytics. It does not name that sibling explicitly, so an agent must infer the distinction from the resource noun.

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 only implied: the agent can tell this is the analytics call for an existing shortlink, but there is no explicit statement of when to use it versus get_profile_analytics, nor any prerequisite (e.g., the link must exist). No exclusions are given.

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

All URLinks 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