Writing a good request
A good request gives the agent the public link of the content, the platform and your goal. The number of Creatypes, the depth, the model, the comment volume and the output language can be specified too.
For example: “Analyse the audience of this TikTok video in English, prepare a quote with 7 precise Creatypes and show it to me before running it.”
The recommended flow
- 1 The agent reads your account and the live rates.
- 2 It creates the pre-scan of the content and waits for the quote to be ready.
- 3 It presents the quote, the parameters and the applicable limits.
- 4 You explicitly confirm that the analysis can start.
- 5 The agent starts the analysis, follows its state, then reads the finished result.
- 6 It reports the Creatypes, themes, requests, feedback and collection figures relevant to your question.
Automatically confirming every quote removes the only moment where the amount and the parameters are still visible. Keeping it manual is safer.
Available MCP tools
Some clients display the technical tool names. They match the steps of the flow.
creatype_account
creatype_rates
creatype_list_searches
creatype_create_search
creatype_get_search
creatype_confirm_search
creatype_wait_for_search
creatype_cancel_searchWaiting, cancelling and resuming
- Waiting for a new state with the MCP tool adds no cost.
- An analysis can be cancelled during the scan, the quote, the queue or the processing; the work actually done still counts.
- After a network drop, the agent must reuse the same idempotency key to resume the same operation without duplicating it.
- A finished analysis stays available in the web app history and can be read again later through MCP.
If the agent no longer sees Creatype
- Check under Settings, then MCP, that the connection or the token is still active.
- Reconnect the web integration if the authorisation was revoked.
- For a local client, create a new token if the secret was lost or replaced.
- Check that the configured address is exactly https://api.creatype.cc/mcp.