I'm half-answering this question with a tiny script that should work in theory.
It searches for a string in --waiting-content, get the IDs and sends them to --schedule-next.
Sadly, it doesn't work because the "u1sdtool --schedule-next" command is failing on a dbus bug and because of this bug report, I don't see a bright future for it.
if [ $1 ]
echo "You need to provide a search string: u1up <search>"
FirstResult=$(u1sdtool --waiting-content | grep -i $search)
if [ $FirstResult ]
node_id=$(echo $FirstResult | sed -n 's/.*node_id=\(.*\)\ share.*/\1/p')
share_id=$(echo $FirstResult | sed -n 's/.*share_id=\(.*\)\ path.*/\1/p')
path=$(echo $FirstResult | sed -n 's/.*path=\(.*\)/\1/p')
echo "Attempting to prioritize $path ..."
u1sdtool --schedule-next=$share_id $node_id
echo "Your search did not match any file waiting in the Ubuntu One queue."
That was an interesting question!