Skip to main content
Glama

Przypominamy.com SMS

by io.github.pawelmamcarz
OverviewDiscussionsAdmin

Kliknięcia w linki

list_links
Read-onlyIdempotent

List tracked links

List click stats for {{link:https://…}} short links from sent messages. Filter by message_id or clicked=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaks. liczba rekordów, domyślnie 50.
clickedNotrue = tylko linki, które ktoś kliknął.
message_idNoId wiadomości msg_…: tylko linki z tej wysyłki.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoStrona rekordów
next_cursorNoKursor kolejnej strony

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / message_id / description
      Previous value: -"Id wiadomości msg_… — tylko linki z tej wysyłki."New value: +"Id wiadomości msg_…: tylko linki z tej wysyłki."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "description": "Strona rekordów",
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Kursor kolejnej strony",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / clicked / description
      Added value: +"true = tylko linki, które ktoś kliknął."
    • addedInput schema / properties / limit / description
      Added value: +"Maks. liczba rekordów, domyślnie 50."
    • addedInput schema / properties / message_id / description
      Added value: +"Id wiadomości msg_… — tylko linki z tej wysyłki."
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the contextual scope of 'links from sent messages' but does not disclose additional behaviors like pagination, rate limits, or auth requirements; output schema handles return shape.

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 description is short and front-loaded, with the core purpose stated first. There is minor redundancy between 'List tracked links' and 'List click stats...', and the {{link:https://…}} placeholder is slightly cryptic, but overall it is appropriately sized.

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 read-only list tool with three optional parameters, a complete input schema, and an output schema, the description is sufficient for correct invocation. It covers the object type, source scope, and available filters without demanding extra prerequisites.

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 baseline is 3. The description mentions message_id and clicked filters, but these are already fully documented in the schema and no new meaning or combination rules are added.

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 clearly states the resource: tracked links and click stats for short links from sent messages. This is specific enough to distinguish from generic sibling list tools like list_messages, though it does not explicitly name an alternative.

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?

The use case is clear: retrieve click stats for links from sent messages, optionally filtered by message_id or clicked=true. It gives actionable filtering context without explicit exclusions or sibling comparisons, which keeps this at a 4 rather than 5.

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

All Przypominamy.com SMS 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