Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_marketplace_order_messages

Retrieve messages for a Discogs marketplace order to track communication and manage transactions.

Instructions

Get a list of an order's messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo
sortNo
sort_orderNo
order_idYes

Implementation Reference

  • MCP tool handler for 'get_marketplace_order_messages'. Instantiates MarketplaceService and delegates to its getOrderMessages method, returning JSON-stringified result or formatted error.
    export const getMarketplaceOrderMessagesTool: Tool<
      FastMCPSessionAuth,
      typeof OrderMessagesParamsSchema
    > = {
      name: 'get_marketplace_order_messages',
      description: `Get a list of an order's messages`,
      parameters: OrderMessagesParamsSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          const messages = await marketplaceService.getOrderMessages(args);
    
          return JSON.stringify(messages);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod input schema for the tool parameters, combining general query params with required order_id.
    export const OrderMessagesParamsSchema = QueryParamsSchema().merge(OrderIdParamSchema);
  • Registers the tool with the FastMCP server instance.
    server.addTool(getMarketplaceOrderMessagesTool);
  • MarketplaceService method implementing the core logic: makes authenticated GET request to Discogs `/orders/${order_id}/messages` API, validates and returns paginated messages.
    async getOrderMessages({
      order_id,
      ...options
    }: OrderMessagesParams): Promise<OrderMessagesResponse> {
      try {
        const response = await this.request<OrderMessagesResponse>(`/orders/${order_id}/messages`, {
          params: options,
        });
    
        const validatedResponse = OrderMessagesResponseSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to get order messages: ${String(error)}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'Get[s] a list', implying a read-only operation, but doesn't specify if it's paginated (hinted by page/per_page parameters), requires authentication, has rate limits, or what the output format is. This leaves significant gaps for a tool with multiple parameters and no output schema.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 complexity (5 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain parameter usage, behavioral traits like pagination or authentication, or output format, leaving the agent with insufficient information to use the tool effectively beyond basic intent.

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 schema provides no parameter descriptions. The tool description adds no information about parameters beyond implying 'order_id' is needed for 'an order's messages'. It doesn't explain the purpose of page, per_page, sort, or sort_order, failing to compensate for the low schema coverage.

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 verb 'Get' and the resource 'list of an order's messages', making the purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'get_marketplace_order' or 'create_marketplace_order_message', which would require more specificity about scope or output format.

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. It doesn't mention prerequisites (e.g., needing an order_id), exclusions, or how it relates to sibling tools like 'get_marketplace_order' or 'create_marketplace_order_message', leaving the agent to infer usage from context alone.

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