Skip to main content
Glama

ShopAt UK Deals

Live Digidip outbound clicks

list_outbound_clicks
Read-only

Live feed of Digidip-wrapped outbound clicks on ShopAt (/go and /voucher/go). MCP-distributed go_url values include ?via=mcp and appear with channel=mcp. Returns recent clicks plus hour/day/MCP/site counts. Digidip admin also shows this live.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
channelNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the bar is lower. The description does add real behavioral content: it discloses what the result contains (recent clicks plus hour/day/MCP/site counts) and explains how ?via=mcp links map to channel=mcp. What it omits is freshness/latency of the 'live' feed and whether counts are bounded by the limit parameter.

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?

Three tight sentences, front-loaded with the resource and scope, then the channel mapping, then return content. Almost every clause carries information. The closing 'Digidip admin also shows this live' is the weakest sentence — mildly useful provenance, but bordering on 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, no-required-args, read-only tool with no output schema, the description supplies the essentials: what is counted, how channel values relate to link provenance, and roughly what comes back. The unanswered pieces are the meaning of the limit cap against the aggregate counts and the site/admin channel distinctions, which are minor but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden and does explain the non-obvious enum semantics: MCP-distributed go_url values carrying ?via=mcp surface as channel=mcp. That is meaning the bare enum list cannot convey. It leaves limit (default 40, max 100) and the site/admin channel values unexplained, so it does not fully compensate for the coverage gap.

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 gives a specific verb+resource pair — a live feed of Digidip-wrapped outbound clicks — and even names the ShopAt routes (/go and /voucher/go) that produce them. An agent knows immediately this reports click activity rather than voucher or store data. It does not explicitly contrast itself with a sibling, which keeps it just below the top mark.

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 rather than stated: the word 'live' and the note that MCP-distributed go_url values appear with channel=mcp suggests monitoring recent click activity, including MCP-sourced traffic. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for historical or non-outbound click analysis. The 'Digidip admin also shows this live' line adds provenance context but not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources