Skip to main content
Glama

ForthClear Liquidation Marketplace

Export orders as CSV

bulk_export_orders
Read-only

Download your orders as CSV, with order id, product, buyer, quantity, total, status, and date. Requires sign-in with seller access. Only orders you own are included. OAuth discovery: /.well-known/oauth-authorization-server (scope seller:read).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_ids": "<order_ids>"
    },
    "name": "bulk_export_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idsYesOrder ids belonging to the calling seller (max 200/request). Orders owned by anyone else are skipped.

Output Schema

NameRequiredDescriptionDefault
csvYes
filenameYes
content_typeYes
skipped_countYes
included_countYes
requested_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "content_type": {
      +      "type": "string"
      +    },
      +    "csv": {
      +      "type": "string"
      +    },
      +    "filename": {
      +      "type": "string"
      +    },
      +    "included_count": {
      +      "type": "integer"
      +    },
      +    "requested_count": {
      +      "type": "integer"
      +    },
      +    "skipped_count": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "filename",
      +    "content_type",
      +    "included_count",
      +    "requested_count",
      +    "skipped_count",
      +    "csv"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / order_ids / description
      Added value: +"Order ids belonging to the calling seller (max 200/request). Orders owned by anyone else are skipped."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-destructive, closed-world operation, but the description adds meaningful context: seller sign-in is required, only owned orders are included, and the OAuth scope is seller:read. It does not discuss rate limits or error behavior, but it goes beyond what the annotations provide.

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 definition is front-loaded with the action, format, and exported fields, then moves to auth and scope requirements. All three sentences are useful and no wording is redundant.

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

Completeness5/5

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

For a one-parameter CSV export tool with annotations and an output schema, the description covers what is exported, who can call it, ownership scoping, and auth scope. Nothing essential for correct invocation appears to be missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the single order_ids parameter is already documented in the schema, including the 200-order maximum and the skipping of orders not owned by the caller. The description adds no additional parameter semantics beyond that baseline.

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?

Names a specific verb ('Download'), resource ('orders'), output format (CSV), and enumerates the included columns. The required order_ids selection and CSV-export framing distinguish it from a generic order-listing tool without relying on a sibling name.

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 does not say when to use this tool versus list_my_orders, list_seller_orders, or other order tools, nor does it state when not to use it. Usage is only implied by the CSV export format and the required list of order ids.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources