Skip to main content
Glama
framinosona

BetaSeries MCP Server

by framinosona

BetaSeries: members

betaseries_members

Manage BetaSeries member accounts: search members, edit profiles, upload avatars, handle notifications, reset passwords, and adjust settings.

Instructions

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

Available operations:

  • delete-members-avatar [DELETE /members/avatar]: Deletes user avatar. Params: no parameters

  • delete-members-banner [DELETE /members/banner]: Remove the banner. Params: no parameters

  • delete-members-notification [DELETE /members/notification]: Deletes a notification. Params: id? (Notification ID)

  • delete-profile-filters-filter [DELETE /profile-filters/filter]: Deletes filter. Params: type? (Type of media (show or movie))

  • get-members-badges [GET /members/badges]: Displays member badges. Params: id? (Member ID)

  • get-members-email [GET /members/email]: Retrieve the email address. Params: no parameters

  • get-members-infos [GET /members/infos]: Returns member information. Params: id? (Member ID (optional))

  • get-members-is-active [GET /members/is_active]: Checks token activity. Params: no parameters

  • get-members-notifications [GET /members/notifications]: Displays latest notifications. Params: since_id? (Last ID (Optional)), number? (Number of notifications, maximum 100 (Optional, default 10)), sort? (Descending or ascending sort (ASC or DESC, default DESC)), types? (Return only certain types separated by a comma (Optional)), all? (Display all notifications, not just unread ones (Optional, default false)), auto_delete? (Automatic deletion of notifications (Optional, default false)), auto_mark? (Automatic marking of notifications as seen (Optional, default false))

  • get-members-options [GET /members/options]: Retrieves member options. Params: no parameters

  • get-members-search [GET /members/search]: Member search. Params: login? (Username, minimum 2 characters. You can use % as a wildcard.), limit? (Number of results to return. Default 10.)

  • get-members-username [GET /members/username]: Returns available usernames. Params: username? (Username)

  • get-members-year [GET /members/year]: Returns yearly member statistics. Params: id? (Member ID (optional)), year? (Year for the statistics calculation)

  • post-members-avatar [POST /members/avatar]: Uploads and replaces user avatar. Params: avatar? (Image to be used for the user's avatar.)

  • post-members-banner [POST /members/banner]: Uploads user banner. Params: avatar? (Image to be used for the user's banner.)

  • post-members-delete [POST /members/delete]: Initiates account deletion process. Params: no parameters

  • post-members-destroy [POST /members/destroy]: Destroys active token. Params: no parameters

  • post-members-email [POST /members/email]: Change the email address. Params: email? (The new email address)

  • post-members-locale [POST /members/locale]: Change the locale. Params: no parameters

  • post-members-lost [POST /members/lost]: Password reset email. Params: find? (Email address or username)

  • post-members-option [POST /members/option]: Modifies user option. Params: name? (Option name (downloaded, global, specials, notation, timelag, friendship, comment_language)), value? (Option value (1 or 0, for friendship: open|requests|friends|nobody, for episodes_tri: name, date, empty, for comment_language: all, site_locale and locale available on Betaseries))

  • post-members-password [POST /members/password]: Change the password. Params: current_password? (The current password of the member), new_password? (The new password for the member), confirmed_password? (The confirmation of the new password for the member)

  • post-members-signup [POST /members/signup]: Creates new member account. Params: login? (Username), password? (MD5 password — Optional: If not provided, it will be generated and sent in the email), email? (Email address)

  • post-members-sync [POST /members/sync]: Searches members among friends. Params: mails[]? (POST array of email addresses to search)

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It gives one-line summaries like 'Deletes user avatar' or 'Initiates account deletion process' but does not warn about irreversible actions, authentication requirements, token invalidation, or side effects. The mutating POST/DELETE operations are not flagged as potentially destructive.

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 due to 24 operations, but it is well-structured: a brief instruction, then a clear bullet-like list grouping operations by HTTP method. Each operation line is concise. It could be trimmed by removing redundant phrases like 'Displays' vs 'Returns', but overall it is appropriately sized for the tool's complexity.

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?

Given no output schema or annotations, the description should cover the full operational context. It covers operation names and parameters thoroughly, but omits return value shapes, error conditions, authentication prerequisites, and rate limits. For a tool with potentially destructive actions, this incompleteness is a notable gap.

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 an operation enum and a generic 'params' object, so the description is the sole source of parameter-level semantics. It lists each operation's parameter names with meaningful descriptions (e.g., 'login? (Username, minimum 2 characters. You can use % as a wildcard.)'), fully compensating for the schema's lack of detail.

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 members API' and enumerates 24 specific operations with HTTP verbs, resources, and brief action statements. This provides a specific verb+resource pairing that distinguishes it from sibling tools like betaseries_persons or betaseries_shows.

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?

The description implicitly covers usage by listing every operation and its parameters, but it never explicitly states when to prefer this tool over siblings or when not to use it. For example, there is no mention of avoiding destructive operations unless the user has appropriate permissions. Users must infer from the name and operation list that this tool is for member-related actions.

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