Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

move_release_in_user_collection

Move a music release from one folder to another in your Discogs collection to reorganize your catalog.

Instructions

Move a release in a user's collection to another folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
folder_idYes
release_idYes
instance_idYes
destination_folder_idYes

Implementation Reference

  • Defines the MCP tool 'move_release_in_user_collection' including its handler function that uses UserService to move the release.
    export const moveReleaseInUserCollectionTool: Tool<
      FastMCPSessionAuth,
      typeof UserCollectionMoveReleaseParamsSchema
    > = {
      name: 'move_release_in_user_collection',
      description: `Move a release in a user's collection to another folder`,
      parameters: UserCollectionMoveReleaseParamsSchema,
      execute: async (args) => {
        try {
          const userService = new UserService();
          await userService.collection.moveRelease(args);
    
          return 'Release moved successfully';
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining the input parameters for the move_release_in_user_collection tool, extending the deleted params with destination_folder_id.
    export const UserCollectionMoveReleaseParamsSchema =
      UserCollectionReleaseDeletedParamsSchema.extend({
        destination_folder_id: z.number(),
      });
  • Registers the moveReleaseInUserCollectionTool with the FastMCP server.
    server.addTool(moveReleaseInUserCollectionTool);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool performs a 'move' operation, implying mutation, but doesn't disclose behavioral traits such as permissions required, whether the move is reversible, rate limits, or error conditions. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence that front-loads the core action without unnecessary words. It's appropriately sized for the tool's purpose, with zero waste.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, mutation operation), lack of annotations, and no output schema, the description is incomplete. It doesn't cover parameter meanings, behavioral details, or return values, leaving the agent with insufficient context to use the tool effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'user's collection' and 'folder', hinting at parameters like username and folder IDs, but doesn't explain the purpose of each parameter (e.g., instance_id, destination_folder_id) or their relationships. This fails to add meaningful semantics beyond the bare schema.

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?

The description clearly states the action ('move') and resource ('a release in a user's collection'), specifying it's moved to another folder. It distinguishes from siblings like 'add_release_to_user_collection_folder' or 'delete_release_from_user_collection_folder' by focusing on relocation, but doesn't explicitly contrast with them in the description text.

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?

No guidance is provided on when to use this tool versus alternatives like 'edit_user_collection_folder' or 'find_release_in_user_collection'. The description implies usage for moving releases between folders but lacks context on prerequisites, constraints, or sibling tool comparisons.

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/cswkim/discogs-mcp-server'

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