Linnworks MCP by usefulapi

Order retrieval is split across six tools (find by number, find by reference, get by GUID, get open orders details, list open orders, search processed), which are technically distinct but could be confused when an agent needs a specific order. Inventory and reference-data tools are clearly separated. Overall mostly distinct but with one or two confusable pairs.

All 17 tools use the linnworks_ prefix with snake_case verb_noun structure (add_, find_, get_, list_, search_, set_). The only variation is singular/plural nouns (find_order_by_number vs find_orders_by_reference), which is semantically motivated. Very consistent.

17 tools for a full order/inventory platform is slightly above the typical 3-15 range but each tool maps to a distinct resource/action (orders, stock, inventory search, reference lists). No obvious filler; the surface is reasonably scoped.

The set is read-heavy with only two write tools (add_order_note, set_stock_level). Major lifecycle operations like creating/updating orders, processing orders, editing inventory items, or managing suppliers/categories/postal services are absent, leaving notable gaps for an ERP integration.