You are mixing actors and systems. Hotel is a system and is to be shown as a rectangle.
Sorts of room don't belong to the UC diag, if they don't suppose different functioning of the system.
Parameters and states are not to be shown as use cases. They are not ACTIONS.
As for the question in the title, the answer is no. Only you have SEVERAL UC diagrams, not a diagram. And it is OK. The activity diagram is simple enough, it even all is in one swimlane.
When you'll define all agents you'll be able to create more complex activity diagrams, with swimlanes.
Edit for second Use Case diagram:
- Here you are trying to set the SEQUENCE of actions. Use case is not the place for it. Only Who and What, not Where, When, How. You are trying to put everything in the use case diagram. Postpone other questions to later diagrams. Look my answer here: https://stackoverflow.com/a/21408074/715269, a guy had made the opposite mistake - put everything in the Sequence diagram.
- It is great that you thought about the registration. But Login and Registration are use cases and should be between agents, not between use cases
- You have mixed two use cases here: one about reservation and one about real arriving/living in/leaving. Divide them.
- Do not try to put the structure information here. Use case is to be done from the user's point of view, not from programmer's one. Don't try to decide inner problems NOW. You have to define the most common problems correctly, that's all.
I have added the part of use case diagram - reservation only.
And beware, it is NOT full yet even in the sense of actors and use cases - you must have the administration and the bookkeeping of the booking system provider, too. (if the system doesn't belong to the Hotel, of course)