Skip to main content
Glama

history

Retrieve recently played items from the local playback log. Filter by time, media type, artist, or text; paginate results or get a count.

Instructions

List recently played items from the local playback log. Filter with an ISO-8601 window (since/until), media/kind/artist, a free-text match or an exact id; page with limit/offset/order, or ask for a count only. An omitted instance returns all boxes. Reads only the local log — no Kodi call, so it works even when no box is reachable. Returns { "total", "returned", "offset", "truncated", "entries": [ { "at", "instance", "kind", "media", "title", "artist", … } ] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoRestrict to one Kodi instance by key. Omitted returns entries from ALL instances — note this differs from other tools, where an omitted instance means the default box.
sinceNoOnly entries at or after this ISO-8601 time (e.g. "2026-06-01T00:00:00Z"). Omitted = from the beginning of the log. Compute relative windows ("last 7 days") yourself.
untilNoOnly entries at or before this ISO-8601 time. Omitted = up to now.
limitNoMax entries to return (default 50, max 1000). When more match, the reply sets "truncated": true — page the rest with offset.
offsetNoNumber of matching entries to skip before this page — paginate together with limit, keeping the same order.
orderNoResult order: "newest" first (default) or "oldest" first to replay a session in the order it happened.
countNoWhen true, return only the total match count (zero entries) — a cheap "how many times / how much did X play".
mediaNoKeep only entries of this media kind (song/episode/movie/musicvideo/picture/channel) — e.g. "movies only".
kindNoKeep only entries of this broad kind: audio or video — e.g. "what music did I play".
artistNoKeep only entries whose performer contains this (substring, case-insensitive) — the music-by-artist filter ("everything Pink Floyd I played"). Only as good as the captured artist tag.
matchNoFree-text substring (case-insensitive) over an entry's human fields — title, album, show, label and artist — to narrow the log without knowing ids.
idNoExact library id to match ("every time THIS item played"). Ids are per media type, so pair with media; feed back a searchmedia or getplaylist row's id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe instance filter, echoed when one was given.
sinceNoThe window's lower bound, echoed when one was given.
untilNoThe window's upper bound, echoed when one was given.
totalYesFull match count, before any paging.
returnedYesRows in this page.
offsetYesRows skipped before this page.
truncatedYesWhether matches remain beyond this page.
entriesYesThe matching history records.
Behavior5/5

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

Discloses that it reads only local log, requires no Kodi call, works even when no box reachable, and explains the behavior of omitted instance (returns all boxes). Since no annotations are provided, the description fully covers behavioral traits.

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?

The description is dense but well-structured within a single paragraph. It front-loads the main purpose, then systematically covers filters, pagination, behavioral notes, and return format. Every sentence adds value without repetition.

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?

Given high complexity (12 parameters, rich filtering, pagination, output schema), the description is complete. It covers all usage aspects, behavioral notes, and the return structure, leaving no ambiguity for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Adds significant meaning beyond a fully covered schema (100% coverage). For instance, explains that omitted instance differs from other tools, advises computing relative windows for since/until, describes default/max for limit and truncated flag, explains offset pagination, order use case, count as cheap total, media/kind examples, artist substring limitation, match field scope, and id pairing with media.

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?

The description clearly states the tool lists recently played items from the local playback log, with specific verb and resource. It distinguishes from sibling tools like nowplaying, getplaylist, and searchmedia by focusing on historical playback log.

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?

Provides explicit guidance on when to use, including filtering options (ISO-8601 window, media/kind/artist, free-text, exact id), pagination (limit/offset/order), and a note that omitted instance returns all boxes, differing from other tools. Also implies alternatives for library search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laszlopere/mcp-kodi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server