Skip to main content
Glama
framinosona

BetaSeries MCP Server

by framinosona

BetaSeries: movies

betaseries_movies

Manage your movie library on BetaSeries: add, remove, rate, favorite, and mark rewatches. Search, discover, and get details for any movie.

Instructions

Call the BetaSeries "movies" API. Pick an operation and pass its parameters in the params object.

Available operations:

  • delete-movies-favorite [DELETE /movies/favorite]: Remove a favorite movie. Params: id? (ID of the movie to remove.)

  • delete-movies-movie [DELETE /movies/movie]: Remove a movie. Params: id? (Movie ID)

  • delete-movies-note [DELETE /movies/note]: Remove a movie rating. Params: id? (Movie ID)

  • delete-movies-rewatch [DELETE /movies/rewatch]: Unmark a movie as rewatched. Params: id? (Movie ID), all? (Remove all rewatch for the given movie (int 0|1)), date? (Precisely removes the rewatch for the given movie (format Y-m-d H:i:s))

  • get-movies-articles [GET /movies/articles]: Display blog articles about the movie. Params: id? (Movie ID)

  • get-movies-characters [GET /movies/characters]: Retrieve the cast of the movie.. Params: id? (Movie ID)

  • get-movies-discover [GET /movies/discover]: Display movies to discover. Params: type? (Type of discovery: popular, upcoming), limit? (Limit on the number of movies to display (optional, default 100, maximum 200)), offset? (Starting number for the movie list (optional, default 0)), includes? (Add some additional blocks to the return: platforms separated by a comma (optional).)

  • get-movies-favorites [GET /movies/favorites]: Retrieve favorite movies. Params: id? (Member ID, optional, if not specified uses the identified member.), start? (Starting number for the movie list (optional, default 0)), limit? (Limit on the number of movies to display (maximum 1000) (optional)), order? (Specify return order: alphabetical, popularity, added, release, svod (optional, default alphabetical)), summary? (Return only essential movie info (Default false)), includes? (If summary = true, add certain additional blocks to the return: user, notes, platforms separated by a comma (optional))

  • get-movies-genres [GET /movies/genres]: Display all available genres. Params: no parameters

  • get-movies-list [GET /movies/list]: Display the list of all movies. Params: start? (Starting number for the movie list (optional, default 0)), limit? (Limit of movies to display (optional, default 100, max 1000)), order? (Specify return order: alphabetical, popularity (optional)), filter? (Display filter (optional, new=only movies not in the account)), platforms? (IDs of platforms where movies are available), country? (Country for platforms)

  • get-movies-member [GET /movies/member]: Display all movies of a member. Params: id? (Member's ID (optional, default identified member)), state? (0 = to watch, 1 = watched, 2 = do not want to watch (default 0)), released? (0 = unreleased movies, 1 = released movies, 2 = all (default 2)), start? (Starting number for the movie list (optional, default 0)), limit? (Limit of movies to display (maximum 1000) (optional)), order? (Specify return order: alphabetical, popularity, added, release, svod (optional, default alphabetical)), summary? (Return only essential movie info (Default false)), tags? (Retrieve movies with tags separated by a comma (optional)), excluded_tags? (Exclude movies with tags separated by a comma (optional)), includes? (If summary = true, add certain additional blocks to the return: user, notes, platforms separated by a comma (optional)), platforms? (List of platform IDs where the movies must be available (Optional)), with_rewatch? (Indicates if movies to rewatch appear in the list (only when state = 0) for premium users (possible values : 0 or 1. Optional, default 0))

  • get-movies-movie [GET /movies/movie]: Show movie details. Params: id? (Movie ID), tmdb_id? (Movie ID on TheMovieDB), imdb_id? (Movie ID on IMDB), includes? (If summary = true, add some additional blocks to the return: user, notes, platforms separated by a comma (optional).)

  • get-movies-random [GET /movies/random]: Display a random movie. Params: nb? (Number of movies to display, default 1)

  • get-movies-scraper [GET /movies/scraper]: Retrieve movie information. Params: file? (File name to process), number? (Number of results to return (default 1))

  • get-movies-search [GET /movies/search]: Search for a movie. Params: title? (Searched title (optional if order=popularity)), order? (Return order (title|popularity), default title), nbpp? (Number of results per page, default 5, maximum 100), page? (Page number, default 1), recent? (Only movies from the last two years (Default false))

  • get-movies-similars [GET /movies/similars]: Retrieve similar movies. Params: id? (Movie ID), details? (Return movie details (Default false))

  • get-movies-upcoming [GET /movies/upcoming]: Display upcoming movies. Params: limit? (Number of movies (Optional, default 25)), order? (Return order: release_date, popularity (Optional, default release_date))

  • post-movies-favorite [POST /movies/favorite]: Add a favorite movie. Params: id? (ID of the movie to add.)

  • post-movies-movie [POST /movies/movie]: Add or update a movie. Params: id? (Movie ID), mail? (Enable email alerts (0 or 1, default 1)), twitter? (Enable Twitter alerts (0 or 1, default 1)), state? (0 = to watch, 1 = watched, 2 = do not want to watch (default 0)), profile? (Display on profile (0 or 1, default 1)), note? (Movie rating (optional, from 1 to 5))

  • post-movies-note [POST /movies/note]: Rate a movie. Params: id? (Movie ID), note? (Rating from 1 to 5)

  • post-movies-rewatch [POST /movies/rewatch]: Mark a movie as rewatched. Params: id? (Movie ID (You can provide several ids separated by a comma))

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoQuery parameters for the chosen operation, as string key/value pairs. See this tool's description for the accepted parameter names per operation.
operationYesWhich operation to perform
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does describe each operation's effect (remove, add, retrieve) and some parameter-specific behaviors (defaults, limits, conditional requirements). However, it omits broader behavioral context such as authentication requirements, rate limits, idempotency of mutations, or error handling, leaving some ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the content is dense and structured as a bulleted list of operations with consistent formatting. Given the tool covers 21 operations, the length is justified and each line adds necessary detail. It is front-loaded with the API call instruction and organized for easy scanning.

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?

The description covers all operations and their parameters comprehensively, but lacks overarching context such as authentication, rate limits, response format, or pagination behavior beyond parameter defaults. Without an output schema, the description does not clarify what the API returns, leaving the agent partially informed.

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

Parameters5/5

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

The input schema only defines a generic 'params' object, so the description is the sole source of parameter meaning. It provides exhaustive per-operation parameter names, optional markers, defaults, maximums, and format hints (e.g., 'Y-m-d H:i:s'), fully compensating for the schema's generic nature.

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 description explicitly states 'Call the BetaSeries movies API' and enumerates 21 specific operations with clear verbs (delete, get, post) and resources (favorite, movie, note, etc.). It clearly distinguishes this tool from siblings by focusing exclusively on movie-related endpoints.

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 provides a catalog of operations but gives no guidance on when to prefer this tool over sibling tools like betaseries_shows or betaseries_seasons. It does not mention any alternatives, exclusions, or conditions for choosing this tool over others.

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/framinosona/betaseries-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server