Skip to main content
Glama

Views across all videos

get_analytics
Read-only

Retrieves library-wide view analytics: total and per-UTC-day views over a chosen period plus the ten most-viewed videos with links. Use it to track audience trends (Recordful Pro only).

Instructions

Recordful Pro only (check get_status recorder.account.plan first). How the user's whole library is watched: total views and views per UTC day over the last days (default 30), plus the ten most viewed videos in that time with links. Covers the videos the user can see, not those in trash. get_video_activity has one video's detail. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoViews per day over this many days, up to today (1 to 365, default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral context: a plan/entitlement gate requiring a prior get_status check, a UTC-day bucketing convention, and the trash exclusion. It doesn't mention rate limits or whether the ten-video list is truncated when fewer videos exist, which keeps it from a 5.

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?

Front-loaded with the gating condition, then the resource, then the disambiguation, then the read-only note – a sensible priority order for an agent. Slightly dense phrasing (the dotted path "recorder.account.plan") costs a little clarity, but no sentence is filler.

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?

With no output schema, the description carries the burden of describing returns and does so (total views, per-day series, top ten with links), while also covering the entitlement prerequisite and scope boundaries. For a one-parameter read tool with annotations, nothing an agent needs to call it correctly is missing.

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?

There is a single parameter with 100% schema coverage, including bounds and the default of 30, so the schema already does the work and the baseline is 3. The description only adds the "over UTC day" framing and re-states the default, which is marginal added meaning.

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?

"How the user's whole library is watched: total views and views per UTC day... plus the ten most viewed videos with links" names the resource and the exact shape of the answer. It also explicitly separates itself from get_video_activity ("one video's detail") and from trash scope, so an agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

It states the prerequisite before use (Recordful Pro only, check get_status recorder.account.plan first), names the alternative tool and the condition that selects it (get_video_activity for a single video), and excludes trash-only content. Nothing about when to reach for this vs. another tool is left to inference.

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