Skip to main content
Glama

stop

Stops the active player on a Kodi instance and clears the playlist, preventing queued items from playing.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoTarget Kodi instance. Omitted uses the default ("(null)").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesPlayback state; "stopped" means nothing is loaded.
typeNoThe active player kind.
mediaNoReal media type (song/episode/movie/musicvideo/…); "unknown" for an off-library file.
idNoLibrary id of the playing item; -1 when off-library.
fileNoPath of the playing item.
labelNoKodi's display label for the item.
titleNoThe item's title (may be empty).
showtitleNoTV episode: the show's name.
seasonNoTV episode: season number.
episodeNoTV episode: episode number.
albumNoSong: the album name.
artistNoSong: the performers, an array of strings.
trackNoSong: track number on the album.
timeNoPlayback position { hours, minutes, seconds, milliseconds }.
totaltimeNoThe item's duration, same shape as time.
Behavior3/5

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

Discloses side effect (clear playlist) and return format, but does not mention behavior when no active player exists or any potential edge cases. With no annotations, description could be more thorough.

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, front-loaded with main action, concise and to the point. No wasted words.

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?

Complete for a low-complexity tool: describes action, side effect, and return format. Output schema is implied in the description.

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 covers the single parameter (instance) at 100% coverage. Description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states action ('stop the active player') and resource ('target instance'), with explicit side effect ('clear playlist'). Distinguishes from sibling tools like 'pause' by mentioning playlist clearing.

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

Usage Guidelines4/5

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

Implies use for stopping playback entirely (including clearing queue), contrasting with 'pause'. Lacks explicit when-not guidance but context is clear enough.

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