Skip to main content
Glama
framinosona

BetaSeries MCP Server

by framinosona

BetaSeries: collections

betaseries_collections

Manage TV show and movie collections on BetaSeries: create, update, delete, list, subscribe, and toggle notifications for collections.

Instructions

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

Available operations:

  • delete-collections-collection [DELETE /collections/collection]: Delete a collection from the identified user [Premium feature]. Params: id (ID of the collection)

  • delete-collections-subscribe [DELETE /collections/subscribe]: Delete the subscription for the identified user to a collection. Params: id (ID of the collection)

  • get-collections-collection [GET /collections/collection]: Display collection's data. Params: id (ID of the collection to retrieve.)

  • get-collections-list [GET /collections/list]: Display the list of all collections of the member. Params: user_id? (Member's ID (optional, default identified member))

  • get-collections-subscriptions [GET /collections/subscriptions]: Display the list of all collections subscribed by the member. Params: user_id? (Member's ID (optional, default identified member))

  • post-collections-collection [POST /collections/collection]: Create/Update a collection for the identified user [Premium feature]. Params: id? (ID of the collection to update (Mandatory for updating)), name? (Name of the collection (Mandatory for creation)), description? (Description of the collection (Optional)), private? (Indicates if the collection if private (Optional, possibles values : '1' (for private) or '0' (for public, default value when creation))), items? (List of shows/movies for the collection (Mandatory for creation, Optional for edition. Must be a JSON array with format : [{"type": "show", "id": 123, "note": "Note about series"}, {"type": "movie", "id": 456, "note": null}]))

  • post-collections-notifications [POST /collections/notifications]: Toggle the notifications of the subscription for the identified user to a collection. Params: id (ID of the collection)

  • post-collections-subscribe [POST /collections/subscribe]: Subscribe the identified user to a collection. Params: id (ID of the collection)

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
Behavior4/5

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

The description discloses important behavioral traits such as premium feature requirements, optional vs. mandatory parameters, and value constraints (e.g., possible values for 'private'). However, it omits authentication requirements, rate limits, and response formats, leaving some behavioral aspects undisclosed.

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 lengthy but well-organized as a list of operations, each with a clear format. It avoids redundancy and front-loads the core purpose. A table could improve scannability, but the structure is effective.

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?

All eight operations and their parameters are documented, including premium flags and defaults, which is strong for operation selection. However, the lack of return value descriptions and authentication context leaves gaps, particularly with no output schema and a multi-operation surface.

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 schema's generic 'params' object defers to the description for actual parameter names. The description thoroughly documents every operation's parameters, including optional markers, mandatory conditions, and the exact JSON structure for 'items'. This goes far beyond what the schema provides.

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 clearly states 'Call the BetaSeries collections API' and lists eight specific operations with HTTP verbs, making the tool's purpose unambiguous and distinct from sibling tools focusing on other resources.

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 the tool's name and the presence of collection-specific operations, but there is no explicit guidance on when to choose this tool over alternatives or any exclusions. The description does not mention sibling tools or alternative approaches.

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