Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Unignore orders

unignore_orders
Destructive

Restore ignored store orders to the Import list so they can be listed again and included in label batches. Skips order IDs that are not ignored.

Instructions

Put ignored store orders back on the Import list.

Reverses ignore_orders: the orders show in list_import_orders again and create_batch_from_orders can ship them. Up to 500 order ids per call; ids that are not ignored are skipped. Returns how many orders came back and their ids.

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": "unignore_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idsYesOrder ids from list_import_orders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the per-call cap (500 ids), partial-success semantics (non-ignored ids skipped rather than erroring), and the return payload (count plus ids). It does not cover permission/auth requirements. Note: annotations declare destructiveHint=true for what the description frames as a restoration, but this is a conservative safety flag rather than an outright contradiction.

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?

Three short sentences with zero filler: the effect comes first, then the mechanics, then the return value. Front-loaded and easy to scan.

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?

No output schema exists, and the description compensates by describing what comes back (count and ids). For a single-parameter mutation, the size cap, skip behavior, and downstream effects cover everything an agent needs to invoke it correctly.

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% and there is only one parameter, so the schema already carries most of the load. The description still adds value by restating the 500-id ceiling as a per-call operational limit and clarifying that ids must be ignored for anything to happen, which the schema does not convey.

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?

States a specific verb and effect: 'Put ignored store orders back on the Import list.' It also explicitly frames itself as the inverse of the sibling tool ignore_orders, so the agent can distinguish it from related tools like list_import_orders without reading the schema.

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

Usage Guidelines5/5

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

Names the prerequisite state (orders must be ignored; non-ignored ids are skipped) and the downstream consequence (they reappear in list_import_orders and become shippable via create_batch_from_orders). Together these sentences tell the agent exactly when this tool is the right call and what it unblocks.

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