Skip to main content
Glama

pause

Pause the active player on any Kodi instance. Returns a snapshot of current playback state: media, title, artist, and time.

Instructions

Press Pause on the Kodi remote: pause the active player on the target instance. Returns the player-state snapshot { "state", "media", "id", "title", "artist", "time", "totaltime", … }.

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?

Describes the core action (pause) and return value (player-state snapshot). With no annotations, it carries the full burden but lacks details on idempotency or state when already paused.

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: first states purpose and action, second lists returned fields. No redundant information.

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?

Tool is simple (one optional param, output schema exists). Description covers action and return value adequately for an AI agent to invoke correctly.

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 coverage is 100% for the single parameter 'instance'. Description adds no further meaning beyond the schema, meriting baseline score.

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?

Clearly states it pauses the active player on the target Kodi instance, distinguishing it from sibling tools like 'play', 'stop', 'mute'. The verb 'pause' uniquely identifies the action.

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?

No guidance on when to use pause vs alternatives like 'stop' or 'mute'. Does not mention conditions or exclusions.

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