Skip to main content
Glama
rollecode

seerr-mcp

by rollecode

create_media_by_media_id_by_status

Idempotent

Change a media item's status in Overseerr/Jellyseerr using its media ID and the target status. Submit the required request body to apply the update.

Instructions

Update media status.

POST /api/v1/media/{mediaId}/{status}

Args: media_id: Media ID status: New status body: Request payload. Read the matching GET or the /schema endpoint first to see the fields this resource expects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
statusYes
media_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already convey that this is a non-read-only, idempotent, non-destructive operation. The description adds the HTTP method/path and tells the agent to consult GET or /schema before sending a body, but it does not describe status transition semantics, side effects, or permission needs.

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?

The description is compact and front-loaded: clear purpose sentence, endpoint, then parameter list. No filler or redundant content.

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?

Output schema and annotations cover return values and safety behavior, and the body-discovery instruction is helpful. Still, an agent must look elsewhere to learn valid status values, and there is no mention of how this relates to sibling status-update tools. Adequate but with clear gaps.

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?

With 0% schema description coverage, the description must compensate. It labels all three parameters and usefully instructs the agent to read the matching GET or /schema endpoint for the body payload. However, 'media_id: Media ID' and 'status: New status' add little over the property names, and valid status values are not provided.

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?

The opening sentence 'Update media status' names a specific verb and resource, and the embedded endpoint clarifies the exact target. It is clearly distinct from sibling status tools that operate on issues or requests.

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

Usage Guidelines3/5

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

Usage is implied by 'Update media status' and the media_id/status parameters, but there is no explicit guidance on when to choose this tool over alternatives. The body-discovery note is operational rather than a selection rule, and no sibling status-update tool is mentioned.

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

Deploy Server

Other Tools