Agents × jobs

Launch an app with persona accounts with any AI agent

Launch an app with persona accounts from any of 25 agents: several TikTok/Instagram characters, each a managed account with bio link, warming and a 30-d…

An app launch on short video usually runs on personas — "the productivity nerd", "the student", "the parent" — each a real account with its own voice, bio link and content plan. From any MCP-capable agent, each persona is one TokPortal bundle: create_bundle in the launch country, configure_bundle_account with the persona's handle, bio and link_in_bio (your store or deep link), warming terms in the persona's niche, and 30 days of configure_bundle_video slots showing the app in that persona's life. Human managers hold the accounts, so there is no OAuth per persona and no audit; get_analytics_dashboard compares personas.

Try the workflow without spending

For this trial, use the remote MCP endpoint https://app.tokportal.com/api/ext/mcp, local tokportal-mcp 1.15.1 or later, or the REST API. Upgrade and restart an older local server first. Version 1.15.0 does not forward the dry-run header; do not use its write tools for a simulation. If you cannot verify the installed local version, use the remote endpoint or REST.

Use the sandbox for the first attempt. MCP write tools accept dry_run: true as a top-level argument, beside body; REST writes accept the X-TokPortal-Dry-Run: true header. Keep your usual authentication and scopes. Each simulated write validates the request and returns credits_would_charge with credits_charged: 0. Nothing is created or published.

Simulated IDs start with 00000000-0000-4000-8000-. Use them only in later dry-run writes. GET requests read real data, so skip publish-readiness checks and polling for synthetic IDs. Simulations have no cross-call memory and upload URLs are placeholders: do not upload files to them.

To run for real, review the returned price and confirm before the first live write. Bundle creation charges credits immediately; publishing hands the order to a manager. Repeat creation without dry-run mode and use the new real IDs for configuration and publishing. A synthetic ID cannot be reused in a live request.

How it works

Design the cast first: 3–6 personas, each with a country (the app's launch markets), a platform (TikTok, Instagram or both), a handle, a one-line bio ending with a call to action, and a link — TokPortal supports link_in_bio as a URI, so use a tracked link per persona (?utm_content=persona_a) to attribute installs. Create each with create_bundle (account_and_videos, videos_quantity 30–60), or all at once with create_bundles_bulk if they share a country, then personalize each account with configure_bundle_account (username, visible_name, biography, profile_picture_url uploaded via upload_image_from_url, link_in_bio).

Warming matters for personas because the account should look like the person: generate_warming_terms from "college student who studies with Pomodoro apps" gives terms a student would search. Content is per persona: screen recordings of the app, talking-head style clips, before/after — uploaded once via upload_video, then placed with batch_configure_bundle_videos at ≤3 posts per day, captions in the persona's voice, disclose_as_ads: true where your legal team says so. publish_bundle per persona.

Then run it as a portfolio from any MCP-capable agent: get_analytics_dashboard and get_analytics_series per account (account filter) show which persona converts, list_analytics_account_comments reveals objections to answer in the next batch, and add_video_slots extends the winners. Register account.finalized, video.finalized and account.banned webhooks so the agent (or your Slack) knows the state of every persona without polling.

Tool sequence

  1. tokportal_get_credit_costs — Personas × (setup + slots + warming) before committing.
  2. tokportal_create_bundle — One per persona: platform, country, videos_quantity, wants_advanced_warming + terms.
  3. tokportal_upload_image_from_url — Persona avatar → profile_picture_url (purpose profile_picture).
  4. tokportal_configure_bundle_account — username, visible_name, biography, link_in_bio (tracked per persona).
  5. tokportal_batch_configure_bundle_videos — 30-day plan per persona, ≤3/day, persona-voice captions.
  6. tokportal_publish_bundle — Per persona.
  7. tokportal_create_webhook_endpoint — account.finalized, video.finalized, account.banned → your Slack/agent.
  8. tokportal_get_analytics_dashboard — Compare personas (account filter, from/to).
  9. tokportal_list_analytics_account_comments — Objections and questions per persona to feed the next batch.

Pick your agent