Mojo's built-in tools: a complete guideMojo's built-in tools: a complete guide
Mojo, your AI companion in AskMojo, comes equipped with four essential tool categories that let you build powerful, automated workflows without external integrations. This guide explains each tool with a concrete, real-world example.
What it does: Mojo can search the web in real-time to gather current information, verify facts, monitor competitors, or research any topic. Unlike static AI knowledge, web search pulls fresh data from live sources.
Concrete example: A product manager creates a weekly competitive intelligence magik. Every Monday morning, Mojo searches for recent news and announcements from three competitor domains, extracts key product launches or pricing changes, and compiles them into a structured summary. The manager gets current market intelligence without manual browsing or news aggregator subscriptions.
When to use it: Market research, fact-checking, content research, monitoring mentions of your brand, gathering recent statistics, or any task requiring up-to-date information beyond Mojo's training data.
What it does: Mojo can create custom images on demand based on text descriptions. These images are generated fresh each time, allowing you to produce visual content that matches your specific needs and brand guidelines.
Concrete example: A nonprofit communications coordinator builds a social media magik that generates branded graphics for weekly campaign posts. She provides Mojo with brand colors, style guidelines, and the week's message. Mojo generates a consistent-looking image that includes key visual elements—like their logo style, color palette, and thematic imagery—without requiring a designer for every post.
When to use it: Blog headers, social media visuals, presentation graphics, concept illustrations, visual brainstorming, or any scenario where you need custom imagery without stock photos or design software.
What it does: Collections are lightweight databases built into your lab. They store structured data—lists, tables, records—that your magiks can read from and write to. Each collection has defined fields (like "question," "status," or "date") and acts as persistent memory for your lab.
Concrete example: A freelance consultant creates a "Client Questions" collection with fields: question, client_name, date_asked, and answer_status. When a client emails a question, she adds it to the collection. A separate magik reviews the collection weekly, identifies the five most common unanswered questions, and drafts template responses. The collection serves as both a knowledge base and a workflow tracker, turning scattered inquiries into structured, actionable data.
Real data from this lab: This lab currently uses collections for onboarding. The "First steps" collection tracks five onboarding stages (create profile, explore labs, copy a lab, run a magik, invite a teammate) with completion status. The "Starter questions" collection holds eight common use cases (podcast show notes, brand-consistent images, social media scheduling, etc.) tagged by audience type. These collections power guided experiences and personalized recommendations.
When to use it: Tracking tasks, storing research results, building mini-CRMs, logging decisions, managing content calendars, storing user preferences, or any workflow requiring memory across multiple magik runs.
What it does: Scheduled routines let your magiks run automatically on a recurring schedule—daily, weekly, monthly, or custom intervals. Once set up, they execute without manual triggering, turning one-time workflows into automated systems.
Concrete example: A busy parent builds a meal-planning magik that runs every Sunday at 6 P[personne] routine generates a weekly dinner menu based on saved family preferences and dietary restrictions, compiles a shopping list organized by store section, and sends both to the family group chat. What used to take 45 minutes of manual planning now happens automatically, freeing up weekend time while maintaining healthy, organized meals.
When to use it: Weekly reports, daily social media posts, monthly summaries, recurring reminders, automated data collection, periodic backups, or any task you currently do manually on a predictable schedule.
The most powerful magiks combine multiple tools. For example:
Content pipeline: A scheduled routine runs every Thursday, uses web search to find trending topics in your industry, generates a branded header image, and writes the results to a "Content ideas" collection for your review.
Competitor monitoring: A daily routine searches competitor websites, logs findings to a "Competitive intel" collection, and once a month generates a summary report with trend analysis.
Research assistant: You add questions to a collection as they come up. A scheduled magik runs weekly, searches for answers to unresolved questions, and updates the collection with findings.
Data sovereignty: All collections live in your lab. One-click export means you own your data completely—no vendor lock-in.
Tool availability: These tools are native to Mojo; no API keys or external accounts required. They work immediately in any lab you create.
Limitations: Web search accesses publicly available information; it cannot access password-protected content. Image generation follows content policies (no copyrighted characters, public figures, etc.). Collections are designed for thousands of records, not millions—think structured workflows, not enterprise databases.
Experiment: Try one tool at a time. Start with collections to understand structured data, then layer in search or scheduling.
Automate one recurring task: Identify something you do weekly. Build a simple magik using one or two tools to handle it.
Explore public labs: See how others combine these tools. Copy a lab that solves something similar to your need and adapt it.
The tools are simple individually but unlock complex automation when combined. Start small, build what you need, and expand from there.
