Cobber_get__api_bookings – 1 MCP server offers this tool
What it usually takes
anyReference– in 1 of 1clientId– in 1 of 1clientReference– in 1 of 1confirmedFrom– in 1 of 1confirmedTo– in 1 of 1currentPage– in 1 of 1id– in 1 of 1includeChannel– in 1 of 1includeDistributor– in 1 of 1livnReference– in 1 of 1order– in 1 of 1orderDescending– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
OpenAPI MCP Server co.huggingface.eduardoalberton/cobber Retrieve bookings via one of the following references: id, livnReference, clientReference, supplierReference, partyName, or partyEmailAddress. Plus optionally, date the booking was confirmed and date of travel. | anyReference,clientId,clientReference,confirmedFrom,confirmedTo,currentPage,id,includeChannel,includeDistributor,livnReference,order,orderDescending,partyEmailAddress,partyName,productIds,resultsPerPage,supplierIds,supplierReference,travelFrom,travelTo | Not stated |