Skip to main content
Glama

stremio_uninstall_addon

Remove an add-on from your Stremio account by manifest URL or add-on ID to clean up unwanted or broken extensions.

Instructions

Remove an addon from the account by its manifest URL or its addon id.

Input Schema

NameRequiredDescriptionDefault
addonYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the target is 'the account' and how the addon is identified, but says nothing about reversibility, whether reordering or addon profiles are affected, or any auth/permission requirement for a destructive mutation.

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?

One sentence, front-loaded with the action and scope, with the identifier options appended. No filler and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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 need no explanation, and the single parameter's accepted forms are covered. However, for a destructive account mutation with zero annotations, the description should at least indicate irreversibility or re-authentication needs; it leaves that gap unfilled.

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

Parameters4/5

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

Schema description coverage is 0% for the single 'addon' parameter, but the description compensates by stating the accepted forms: a manifest URL or an addon id. That is exactly the detail the schema omits, though it gives no example format for either form.

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 ('Remove an addon from the account') and identifies the two accepted identifiers, which cleanly distinguishes it from siblings like stremio_install_addon, stremio_list_addons and stremio_restore_default_addons. It does not name any sibling explicitly, so it stops short of a 5.

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 description gives no when-to-use or when-not-to-use guidance and never mentions alternatives (e.g., stremio_restore_default_addons when the goal is a full reset, or stremio_install_addon for the inverse operation). Usage is only inferable from the verb itself.

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