Skip to main content
Glama

Reading report

link_report
Read-only

Full reading report for one link: each reader (email, visits, active time, how far they read), time per section, most clicked elements, copied text, rage clicks, views per day, where each reader is (city or region, from their time zone), and the link's settings (who can open, password, downloads, screenshots, their AI, expiry, folder). For a video: how much each viewer watched, the parts they skipped or watched again, who watched each part, and where viewers stop.

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": {
      "link": "<link>"
    },
    "name": "link_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe link: its URL, slug, id or title.

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value on the read side by spelling out what comes back in detail, including per-reader location inferred from time zone and per-section engagement. It does not discuss authorization requirements, size/performance, or failure modes when the link does not exist or has no traffic.

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?

Two sentences total, front-loaded with the scope ('Full reading report for one link') followed by a dense comma-separated content inventory, then a separate sentence for the video variant. Every clause names a distinct piece of returned data, so nothing is wasted.

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?

No output schema exists, so the description bears the burden of describing the return shape, and it does so thoroughly for both link and video cases. Given a single required parameter and read-only annotations, the definition is nearly self-sufficient; only the absence of error/empty-state behavior and alternative-tool routing keeps it shy of complete.

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 coverage is 100% and the single 'link' parameter is already documented as accepting URL, slug, id or title. The description adds nothing about that parameter — no example formats, no ambiguity notes (e.g., what happens if the title is not unique). Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific resource (a full reading report) and pins the scope to exactly one link, then enumerates the report's contents in concrete terms (per-reader visits, active time, rage clicks, views per day, link settings). It lacks an explicit verb like 'get'/'retrieve', but the noun phrase is unambiguous enough that an agent knows what it is. The 'for one link' scoping implicitly distinguishes it from room_report, though it never names that sibling directly.

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: 'for one link' and 'full reading report' suggest using it when a complete per-link analytics dump is needed. There is no explicit when-to-use statement, no when-not, and no pointer to alternatives such as room_report for rooms or reader_activity for individual readers. An agent must infer placement from the sibling names alone.

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