Skip to main content
Glama
Sign In

Snip

by link.snip
OverviewDiscussionsAdmin

Get account stats

get_account_stats
Read-onlyIdempotent

Clicks and QR scans across every link in the user's Snip.link account: totals, by day, the busiest links, and the top countries, referring sites and devices. Needs the user signed in to Snip.link. Use this for questions like "how are my links doing" or "which link got the most scans this week".

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_account_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, up to the plan's limit (30 on Free, a year on Pro). Default 30.
linksNoHow many of the busiest links to list. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is well covered. The description adds useful context beyond annotations by stating that the user must be signed in and by listing the kinds of aggregate data returned.

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?

The description is front-loaded with the collected metrics and scope, then adds the sign-in requirement and usage examples. Every sentence contributes useful information without redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description adequately explains the return categories (totals, daily data, busiest links, countries, referrers, devices). Combined with rich annotations and fully documented parameters, an agent has enough context to call this tool correctly.

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 both parameters (days and links) are fully documented in the schema, so the baseline is 3. The description does not add any additional parameter semantics beyond what the schema already provides.

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 clearly states the resource and scope: clicks and QR scans across every link in the user's account, including totals, daily breakdowns, busiest links, countries, referrers, and devices. This account-wide scope distinguishes it from the sibling get_link_stats, which is link-specific, even without naming it directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage examples such as "how are my links doing" and "which link got the most scans this week," and notes the sign-in prerequisite. However, it does not explicitly name when not to use it or point to get_link_stats as the alternative for single-link questions.

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

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