What does setting up a brand and a campaign through Storika do?
Setting up through Storika's MCP connector gives a workspace a brand with a saved profile and a campaign that creators can be found for. The assistant reads the brand's public website, proposes profile text for the marketer to approve, and sets up the campaign from the details the marketer gives.
What can a marketer ask to set up a brand and a campaign?
A marketer can write: "Set up my brand from our website link, then set up a gifting campaign for our sunscreen on Instagram in the US, using the budget and dates I give you. Creators receive a physical product." Storika needs those details, and the assistant never invents them.
Which Storika connector tools set up a brand and a campaign, and in what order?
Storika's set_up_brand runs first with the website link and reads the site's public pages. set_up_brand runs again with the brand category, and then with sections to save the profile text the marketer approves. setup_campaign runs last, with the campaign's details.
What comes back when Storika sets up a brand and a campaign?
Storika's set_up_brand returns the text of the website's public pages so the assistant can write the brand profile. Its sections call returns the current and the new text with a confirmation_ref. A setup_campaign create call replies with a list of what it stored, and the assistant shows that list to the marketer.
Which brand and campaign setup step waits for the marketer's yes?
Saving brand profile text waits for the marketer's yes: the first set_up_brand sections call in Storika saves nothing, and the second call saves the text after the yes. setup_campaign asks for no yes, because creating a campaign sends nothing and charges nothing. The assistant asks first whether creators receive a physical product. A later creator search charges tokens.
Tools in the order they run
- set_up_brand with website_url: names the brand and the workspace, reads the public pages of that site in the same call and returns the page text. Source calls are for an owner or admin. With only a name it names or adds a brand and reads no site.
- set_up_brand with category: saves the brand category the assistant picked from the page text, in its own call, before the sections call.
- set_up_brand with brand and sections, first call: saves nothing. It returns the current and the new text and a confirmation_ref, and the assistant shows that text to the marketer.
- set_up_brand with brand and sections, second call: after the marketer's yes, the same arguments and the confirmation_ref save the profile text.
- setup_campaign without campaign_id: sets the campaign up at once from one source (address, file_urls, shop_product or shop_products) when the call carries name, type, description, platform, budget, started_at, ended_at, geo_target, needs_shipping_address, and product_name unless a shop product is given. A campaign of type paid_collaboration also requires cost_per_contract, the agreed creator fee. The assistant does not call again to confirm.
- setup_campaign with campaign_id: updates that campaign with the changed fields. Budget, type, needs_shipping_address, platform, geo_target, product_name and commission_rate are fixed once the campaign is set up, so a different value means a new campaign.
Before setting up a campaign the assistant reads the connector's campaign-onboarding-playbook prompt. It calls whoami at the start of a session, never invents the product, brand, budget or dates, and files a campaign once. The assistant fetches tools/list at each new session and follows the live schemas.