Skip to main content
Glama

ForthClear Liquidation Marketplace

Bulk mark orders shipped

bulk_mark_shipped
Destructive

Mark up to 200 of your orders as shipped, with an optional tracking number, tracking link, and carrier applied to the whole batch. Requires sign-in with seller access. Tracking you supply replaces tracking already on those orders, and each buyer is notified. OAuth discovery: /.well-known/oauth-authorization-server (scope seller:write). Sensitive: requires user approval each time.

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_mark_shipped"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idsYesOrder ids belonging to the calling seller (max 200/request). Orders owned by anyone else are skipped.
carrier_nameNoCarrier for the shipment. Omit to infer it from tracking_number.
tracking_urlNoTracking URL written to every listed order.
tracking_numberNoTracking number written to every listed order. Supplying this without carrier_name auto-detects the carrier.

Output Schema

NameRequiredDescriptionDefault
failedYes
carrierYes
successfulYes
failureCountYes
successCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "carrier": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "failed": {
      +      "items": {
      +        "properties": {
      +          "orderId": {
      +            "type": "integer"
      +          },
      +          "reason": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "orderId",
      +          "reason"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "failureCount": {
      +      "type": "integer"
      +    },
      +    "successCount": {
      +      "type": "integer"
      +    },
      +    "successful": {
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "successful",
      +    "failed",
      +    "successCount",
      +    "failureCount",
      +    "carrier"
      +  ],
      +  "type": "object"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / carrier_name / description
      Added value: +"Carrier for the shipment. Omit to infer it from tracking_number."
    • 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."
    • addedInput schema / properties / tracking_number / description
      Added value: +"Tracking number written to every listed order. Supplying this without carrier_name auto-detects the carrier."
    • addedInput schema / properties / tracking_url / description
      Added value: +"Tracking URL written to every listed order."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the concrete destructive behavior: supplied tracking replaces existing tracking on those orders, and each buyer is notified as a side effect. It also adds auth scope and the per-call approval requirement, turning the bare destructiveHint/non-idempotent flags into actionable consequences.

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?

Front-loads purpose, cap, and overwrite semantics in one sentence, then auth and safety details. The raw OAuth discovery URL is a bit of plumbing, but it is short and token-cheap; nothing is padded.

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 destructive, approval-gated bulk mutation, the description covers batch limit, overwrite semantics, buyer notification side effect, and auth requirements; with an output schema present, return values need not be explained. Nothing an agent needs to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds real meaning by noting the tracking/carrier values apply to the whole batch and overwrite existing values, clarifying that carrier can be omitted when tracking_number triggers inference. It slightly restates the schema's 'written to every listed order' wording.

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 ('mark ... as shipped'), the resource (orders), the caller's own scope ('your orders'), and the batch cap ('up to 200'), which immediately separates it from single-order siblings like confirm_order or cancel_order. The optional fields applied to the batch are stated up front.

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

Usage Guidelines3/5

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

States a prerequisite ('Requires sign-in with seller access') and that it is sensitive/approval-gated each time, which shapes when it can be used. It does not say when to prefer this over a single-order path or what to do when some orders are ineligible, beyond the schema's note that foreign orders are skipped.

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