mcp-kodi

Overview Schema Source Related Servers Discussions Admin

stop

Press Stop on the Kodi remote: stop the active player on the target instance and clear the playlist it was playing, so no queued items linger. Returns the player-state snapshot — { "state": "stopped" } after a successful stop.

Instructions

Input Schema

Name	Required	Description	Default
`instance`	No	Target Kodi instance. Omitted uses the default ("(null)").

Output Schema

Name	Required	Description
`time`	No	Playback position { hours, minutes, seconds, milliseconds }.
`type`	No	The active player kind.
`audio`	No	Audio tracks of the playing video (video only): { count, current: { index, language, codec, channels } }. `index` is the set_audio_and_subtitle audio selector.
`state`	Yes	Playback state; "stopped" means nothing is loaded.
`progress`	No	Legible position derived from time/totaltime, "elapsed / total (NN%)" e.g. "15:38 / 46:40 (33%)"; absent for live streams with no fixed length.
`subtitle`	No	Subtitles of the playing video (video only, present only when any exist): { count, enabled, current: { index, language } }. `current` is present only while a subtitle is shown; `index` is the set_audio_and_subtitle subtitle selector.
`totaltime`	No	The item's duration, same shape as time.
`nowplaying`	No	The loaded media (present whenever something is loaded): { media (song/episode/movie/…; "unknown" off-library), id (library id, -1 off-library), file, label, title; and where they apply showtitle/season/episode (TV), album/artist/track (song) }.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 13, 2026

removedOutput schema / properties / album

Removed value: -{
-  "description": "Song: the album name.",
-  "type": "string"
-}

removedOutput schema / properties / artist

Removed value: -{
-  "description": "Song: the performers, an array of strings.",
-  "type": "array"
-}

addedOutput schema / properties / audio

Added value: +{
+  "description": "Audio tracks of the playing video (video only): { count, current: { index, language, codec, channels } }. `index` is the set_audio_and_subtitle audio selector.",
+  "type": "object"
+}

removedOutput schema / properties / episode

Removed value: -{
-  "description": "TV episode: episode number.",
-  "type": "integer"
-}

removedOutput schema / properties / file

Removed value: -{
-  "description": "Path of the playing item.",
-  "type": "string"
-}

removedOutput schema / properties / id

Removed value: -{
-  "description": "Library id of the playing item; -1 when off-library.",
-  "type": "integer"
-}

removedOutput schema / properties / label

Removed value: -{
-  "description": "Kodi's display label for the item.",
-  "type": "string"
-}

removedOutput schema / properties / media

Removed value: -{
-  "description": "Real media type (song/episode/movie/musicvideo/…); \"unknown\" for an off-library file.",
-  "type": "string"
-}

addedOutput schema / properties / nowplaying

Added value: +{
+  "description": "The loaded media (present whenever something is loaded): { media (song/episode/movie/…; \"unknown\" off-library), id (library id, -1 off-library), file, label, title; and where they apply showtitle/season/episode (TV), album/artist/track (song) }.",
+  "type": "object"
+}

addedOutput schema / properties / progress

Added value: +{
+  "description": "Legible position derived from time/totaltime, \"elapsed / total (NN%)\" e.g. \"15:38 / 46:40 (33%)\"; absent for live streams with no fixed length.",
+  "type": "string"
+}

removedOutput schema / properties / season

Removed value: -{
-  "description": "TV episode: season number.",
-  "type": "integer"
-}

removedOutput schema / properties / showtitle

Removed value: -{
-  "description": "TV episode: the show's name.",
-  "type": "string"
-}

addedOutput schema / properties / subtitle

Added value: +{
+  "description": "Subtitles of the playing video (video only, present only when any exist): { count, enabled, current: { index, language } }. `current` is present only while a subtitle is shown; `index` is the set_audio_and_subtitle subtitle selector.",
+  "type": "object"
+}

removedOutput schema / properties / title

Removed value: -{
-  "description": "The item's title (may be empty).",
-  "type": "string"
-}

removedOutput schema / properties / track

Removed value: -{
-  "description": "Song: track number on the album.",
-  "type": "integer"
-}

First observedv0.1.0Jun 14, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the important non-obvious side effect: the playlist is cleared so queued items don't linger, which matters because stop is more disruptive than pause. It omits permission/auth requirements and error behavior, so it isn't fully transparent.

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?

Two tight sentences, front-loaded with the action and then the side effect. The trailing return-value sentence is largely redundant given the output schema exists, which is the only real waste.

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 single-optional-param tool with a 100%-covered schema and an output schema, the description covers the action and the destructive playlist-clearing behavior. It does not need to explain return values, and the lack of annotations is partly compensated by the stated side effect.

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 only one optional parameter and schema coverage is 100%, so the schema already documents `instance` and its default. The description adds only the phrase 'target instance', which is marginal beyond the structured field.

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?

States a specific verb and resource — stop the active player on the target instance — and names the key side effect (clearing the playing playlist). That effect implicitly distinguishes it from the sibling `pause`, though no sibling is ever named explicitly.

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 'Press Stop on the Kodi remote' framing gives context for when a user would reach for it, but there is no explicit when-to-use, when-not-to-use, or comparison against `pause`/`dropplaylists`, which are the obvious adjacent choices.

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