Add a movie or series to your Stremio library using its IMDb ID. Re-adding a removed title restores it with its previous watch state.
Add a movie or series to the account library by IMDb id.
Re-adding a title that was removed restores it with its watch state.
| Name | Required | Description | Default |
|---|---|---|---|
| imdb_id | Yes | ||
| content_type | No | movie |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses that re-adding a removed title restores its watch state (an idempotent-restore trait), but omits auth requirements, what happens if the title is already present, and error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two front-loaded sentences with zero waste; the core action leads and the restore nuance follows as supporting detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values needn't be explained, and the restore behavior is a helpful addition for a mutation tool. Only minor gaps remain: no auth note and no already-in-library behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It clarifies the imdb_id format ('by IMDb id') and implies the content types ('movie or series'), but never maps them to the content_type parameter or notes its default, leaving that parameter effectively undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Add'), resource ('movie or series to the account library'), and key ('by IMDb id'). This clearly separates it from stremio_remove_from_library and stremio_get_library. It stops just short of explicitly naming those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the action (adding to library), and the restore-on-re-add sentence hints at a useful edge case. However, it never states when to prefer this over stremio_mark_watched or how it relates to stremio_get_library, leaving alternatives to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.