I’ve heard it said that “Maya is written in MEL,” and while that’s not strictly true in every sense, it might give you an idea of how Maya and MotionBuilder are different. In Maya, nearly every action you perform as a user is a MEL command in some form or another. When you use the Create Polygon Cube tool, the polyCube command is actually being called as a result, so Maya can happily show that to you. In MotionBuilder, however, while dragging out a cube from the Asset Browser and calling FBCube() have essentially the same effect, they are entirely separate approaches – creating a cube via the UI does not make any Python calls. The UI cuts straight to MotionBuilder’s slimy, gooey, compiled-bytecode guts, which it can’t echo to you in any helpful way.
Here is a crude and hilariously over-simplified diagram to illustrate:
UI
|
MEL UI Python
| \ /
Maya Mobu
I’d recommend diving into the MotionBuilder Python API Documentation:
http://download.autodesk.com/global/docs/motionbuildersdk2012/en_US/index.html?url=py_ref/annotated.html,topicNumber=py_ref_annotated_html
Specifically check out the samples and the class reference for whatever classes you think might be related to the task you’re trying to accomplish.