As Cap said, if you have the outgoing personality and leadership needed to play games then by all means do it. If you don't have the desire to act like a game show host, just keep quiet.
I don't think it's a matter of "capability" as much as it's a matter of pulling it off without potentially turning someone's wedding into a circus.
Just like many of you, I am perfectly capable of hosting a "game show style" event. I simply choose not to at *most* of my weddings. My reasons for doing so are:
(1) While the client may find making dinner "interactive" entertaining, do they truly know what their guests will find entertaining? The truth is, people get "hangry". As I explain to my couples (in the nicest, most tactful way possible) when they inquire about these things is basically, your guests have been sitting around all day, (getting ready>driving to your ceremony>sitting through the prelude/ceremony/postlude>sitting through cocktail hour>depending on how we configure your timeline, sitting through your formal dances etc.). Some people just want to get their food and move on to the next event by this time. Pair this with the fact some people are being reunited with family and friends they haven't seen in a long time, and you're potentially interrupting them. Personally, I am not entertained when interrupted.
(2) It's not always easy to pull off. Again, I am not saying that we are incapable of doing it. What I am saying is sometimes people simply aren't in the mood. If it's a late dinner - people will be hungry. If it's the hottest day of the year in a venue with no AC - people probably won't have the patience. Sometimes the layout of the hall is not conducive to such things. Sometimes the energy just isn't there at a wedding for factors beyond your control (death, family disagreements etc.). Even if you can pull it off, now we have to find something that appeals to the majority - not everyone in attendance might be into movies, sports or even know the bride or groom that well. I do not want to "build up" something with a couple that might flop. Generally, a flop looks bad on the performer.
(3) We are a no-cheese Dj service. This is how we advertise and how we plan. The focus is on the client and their family and not us at weddings. Therefore, the clients we speak with are largely those that see "Cheese" Djs and associate such acts with their performances and want the opposite. Our main target audience and market is the client who wants a fun, yet classy custom event, and these are the people we wish to continue to attract. At the end of the day this is the way I choose to run my company, however, it does not mean I am stuck in my ways. My company will contract our AV equipment, photobooths and videographers separate of the Dj service (although, I am not sure how much longer I plan to contract the other services indepently for). As a result, I have had a front row ticket to some of my competitors' performances. I have seen some Djs who are truly top-notch in my opinion, as well as some who are awful (typically when I observe someone top-notch I get a card and try to recruit). Ultimately, this gives me a chance to see their "successes" and "failures" as well. In my opinion, I haven't seen these types of things go over "well" a lot firsthand.
At times I do contradict (notice how above I stated "I simply choose not to at *most* of my weddings"). Things I keep in mind are:
(1) There's a place and a time for everything. For example, if I had a movie themed wedding, it might make sense to have trivia. If I have a sports themed wedding, then sports trivia or some kind of basket shooting contest might add to the atmousphere. The difference here is the event is already "set up" for it and I am not introducing something irrelevant or unrelated.
(2) If the bride and groom insist even after discussion. Ultimately the client is the boss, and accommodating their requests from an entertainment standpoint (within reason) is our job. I am not going to decline something that is important to the couple just because it is not how we do things, but I will push to make sure they make an informed decision.
As far as table dismissals, again, I choose to do table "touches" and interact that way. Who is responsible for table dismissal is always something I cover in my final walkthrough. I would NEVER turn down doing this for the following reasons:
(1) I take a stance that if there is no hall coordinator or wedding planner, it is our job to coordinate. Sometimes, buffet dismissal falls under this umbrella (especially when the other vendors don't have the staff for it).
(2) People have different budgets. Sometimes they cut back on using a caterer and used someone from church or whatever to allocate more money to your services.
(3) Barn weddings etc. are increasingly popular around here. Along with them come more 'DIYers' (friends, family, etc. doing the cooking who don't know the first thing about weddings). I have a wedding next month that will feature four caterers with food stations - it makes more sense for me to do dismissals as it will be centralized rather than let four other vendors trip over each other.
As others have mentioned, this is probably a regional thing as well as a budget/pricepoint thing. What I'm doing here in Ohio might not work out the same in LA or NYC.
