Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

edit_marketplace_order

Update the status, shipping cost, or other details of a Discogs marketplace order to manage sales transactions.

Instructions

Edit a marketplace order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes
statusNo
shippingNo

Implementation Reference

  • Defines the 'edit_marketplace_order' tool handler, including name, description, parameters schema, and execute function that delegates to MarketplaceService.editOrder.
    export const editMarketplaceOrderTool: Tool<FastMCPSessionAuth, typeof OrderEditParamsSchema> = {
      name: 'edit_marketplace_order',
      description: 'Edit a marketplace order',
      parameters: OrderEditParamsSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          const order = await marketplaceService.editOrder(args);
    
          return JSON.stringify(order);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Implements the core logic for editing a marketplace order by making a POST request to the Discogs API endpoint `/orders/${order_id}` and validating the response.
    async editOrder({ order_id, ...body }: OrderEditParams): Promise<OrderResponse> {
      try {
        const response = await this.request<OrderResponse>(`/orders/${order_id}`, {
          method: 'POST',
          body,
        });
    
        const validatedResponse = OrderResponseSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to edit order: ${String(error)}`);
      }
    }
  • Zod schema defining the input parameters for editing a marketplace order: order_id (from OrderIdParamSchema), optional status and shipping.
    export const OrderEditParamsSchema = OrderIdParamSchema.extend({
      status: OrderStatusSchema.optional(),
      shipping: z.number().optional(),
    });
  • Registers all marketplace tools with the FastMCP server, including the editMarketplaceOrderTool.
    export function registerMarketplaceTools(server: FastMCP): void {
      server.addTool(getUserInventoryTool);
      server.addTool(getMarketplaceListingTool);
      server.addTool(createMarketplaceListingTool);
      server.addTool(updateMarketplaceListingTool);
      server.addTool(deleteMarketplaceListingTool);
      server.addTool(getMarketplaceOrderTool);
      server.addTool(editMarketplaceOrderTool);
      server.addTool(getMarketplaceOrdersTool);
      server.addTool(getMarketplaceOrderMessagesTool);
      server.addTool(createMarketplaceOrderMessageTool);
      server.addTool(getMarketplaceReleaseStatsTool);
    }
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. 'Edit' implies a mutation operation, but the description doesn't disclose what permissions are required, whether changes are reversible, what happens when status changes occur, or any rate limits or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at just 4 words with no wasted language. While this conciseness comes at the expense of completeness, the description is efficiently structured with the core action stated first.

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

Completeness1/5

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

For a mutation tool with 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool does beyond the name, provides no behavioral context, offers no parameter guidance, and gives no indication of what the tool returns or when to use it.

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?

The description provides no parameter information beyond what's implied by the tool name. With 0% schema description coverage and 3 parameters (order_id, status with enum values, shipping), the description fails to explain what these parameters mean, what the status enum represents, or how shipping values should be formatted. It doesn't compensate for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Edit a marketplace order' is a tautology that essentially restates the tool name 'edit_marketplace_order' without providing additional specificity. It doesn't distinguish this tool from sibling tools like 'update_marketplace_listing' or clarify what aspects of an order can be edited versus other marketplace operations.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. There are multiple marketplace-related sibling tools (create_marketplace_listing, get_marketplace_order, update_marketplace_listing, etc.), but the description offers no context about when this specific edit operation is appropriate versus those other tools.

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