Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_stats

Read-only

Retrieves read-only statistics for videos, channels, playlists, downloads, watch activity, download history, and biggest channels in a Tube Archivist archive.

Instructions

Library, download, and watch statistics. Reads only. Actions: video (GET /api/stats/video/), channel (GET /api/stats/channel/), playlist (GET /api/stats/playlist/), download (GET /api/stats/download/), watch (GET /api/stats/watch/), download_history (GET /api/stats/downloadhist/), biggest_channels (GET /api/stats/biggestchannels/).

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": {
      "action": "<action>"
    },
    "name": "ta_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoorder
actionYesTube Archivist operation to call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description's 'Reads only' repeats the read-only annotation and adds nothing about authentication, rate limits, pagination, data freshness, or response shape; the endpoint list is operational rather than behavioral.

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 front-loaded with the resource summary and read-only note, then lists action/endpoint pairs compactly. The endpoint list is dense but each entry ties an action to a route, and there is no filler.

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

Completeness3/5

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

For a simple read-only stats dispatcher, the description identifies all actions and the annotations cover safety. It omits what statistics each action returns and any semantics for the optional order parameter, which matters because there is no output schema; adequate but incomplete.

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 action enum and optional order parameter are already documented in the schema. The description enumerates each action and maps it to a GET endpoint, which adds some meaning, but it does not explain the optional order parameter or what each action returns, so the baseline 3 is appropriate.

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 that the tool provides library, download, and watch statistics and enumerates seven action values with endpoints, so the verb and resource are clear. It does not explicitly contrast with siblings like ta_library or ta_download, but the action list and 'Reads only' make the scope evident.

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

Usage Guidelines2/5

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

The description only says 'Reads only' and lists actions; it gives no when-to-use conditions, no prerequisites, and no explicit alternatives to ta_library, ta_download, or other sibling tools. The endpoint mapping implies use for metrics, but the agent must infer that.

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