Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

update_marketplace_listing

Modify existing marketplace listings on Discogs by updating details like condition, price, and status to maintain accurate inventory.

Instructions

Update a marketplace listing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idYes
release_idYes
conditionYes
sleeve_conditionNo
priceYes
commentsNo
allow_offersNo
statusYes
external_idNo
locationNo
weightNo
format_quantityNo

Implementation Reference

  • The tool handler (execute function) for 'update_marketplace_listing'. It instantiates MarketplaceService and calls its updateListing method with the input args.
    export const updateMarketplaceListingTool: Tool<
      FastMCPSessionAuth,
      typeof ListingUpdateParamsSchema
    > = {
      name: 'update_marketplace_listing',
      description: 'Update a marketplace listing',
      parameters: ListingUpdateParamsSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          await marketplaceService.updateListing(args);
    
          return 'Listing updated successfully';
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema definition for input parameters of the update_marketplace_listing tool, merging ListingIdParamSchema and ListingNewParamsSchema.
    export const ListingUpdateParamsSchema = ListingIdParamSchema.merge(ListingNewParamsSchema);
  • Registration function that adds the updateMarketplaceListingTool (among others) to the FastMCP server.
    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);
    }
  • The supporting method in MarketplaceService that performs the actual Discogs API POST request to update the listing.
    async updateListing({ listing_id, ...body }: ListingUpdateParams): Promise<void> {
      try {
        await this.request<void>(`/listings/${listing_id}`, {
          method: 'POST',
          body,
        });
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to update listing: ${String(error)}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' which implies a mutation operation, but it doesn't disclose any behavioral traits such as permission requirements, whether updates are reversible, rate limits, or what happens to unspecified fields. This leaves significant gaps for an agent to understand the tool's behavior.

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 extremely concise with just four words, which is front-loaded and wastes no space. However, it's arguably too brief given the tool's complexity (12 parameters, mutation operation), bordering on under-specification rather than optimal conciseness.

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 (12 parameters, 5 required, mutation operation), no annotations, and no output schema, the description is incomplete. It doesn't address key contextual aspects like what a marketplace listing entails, the impact of updates, or expected outcomes. For a tool with this level of detail in the input schema, the description should provide more guidance.

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 schema description coverage is 0%, meaning none of the 12 parameters are documented in the schema. The description adds no meaning beyond the tool name—it doesn't explain what parameters like 'condition', 'sleeve_condition', or 'status' represent, nor does it clarify the relationship between 'listing_id' and 'release_id'. This fails to compensate for the lack of schema documentation.

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

Purpose3/5

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

The description 'Update a marketplace listing' clearly states the verb ('update') and resource ('marketplace listing'), but it's vague about what aspects can be updated and doesn't distinguish this tool from its sibling 'edit_marketplace_order' or 'edit_user_collection_custom_field_value'. It provides a basic purpose but lacks specificity about the listing's scope or context.

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 no guidance on when to use this tool versus alternatives like 'create_marketplace_listing' or 'delete_marketplace_listing', nor does it mention prerequisites such as needing an existing listing ID. It lacks any context about usage scenarios or exclusions.

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