create_units

writes

One of the tools an AI assistant can call on an Avrosh account.

What it does

Add units of capacity to a bookable type. A unit is whatever can only take one booking at a time - a room, a chair, a bay, one person's calendar. HOW MANY YOU CREATE IS HOW MANY BOOKINGS FIT IN THE SAME SLOT: one unit means strictly one at a time. A type with no units is never offered to a customer, so create at least one after create_bookable_type or the type does nothing. Labels are what staff see on the board and must be unique within the business; a clash is refused with the labels that already exist, and nothing is created.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

bookable_type_idstringrequired

From list_bookable_types. The type these units carry.

labelsarrayrequired

One label per unit, in the operator's own words - 'Chair 1', 'Room 204', 'Bay A'. The number of labels IS the number of units. Max 50 at a time.

Response

The result arrives as an MCP content block; the JSON in the panel is what the text field parses to.

Connecting

Point any MCP client at https://us.avrosh.com/mcp and log in — OAuth 2.1, no key to paste.

The panel here uses the other door: a bearer key made in the dashboard, for a script or a cron job with no browser to sign in with. Both reach the same endpoint. Full notes on the reference overview.

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "create_units",
      "arguments": {
        "business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
        "bookable_type_id": "a41c...",
        "labels": [
          "Chair 1",
          "Chair 2"
        ]
      }
    }
  }'