AdviblyMCP limits
Account entitlements and server-side limits that affect MCP tool calls.
Brands
| Plan | Brands |
|---|---|
| No subscription | 1 |
| Create | 1 |
| Publish | 5 |
| Studio | Unlimited |
Quick brands created through advibly_quick_brand do not count against the
regular brand limit.
Before onboarding another regular brand, call advibly_list_brands. If the
plan is at its limit, reuse the existing brand or resolve the entitlement
instead of retrying the same call.
Social accounts
advibly_social_list_accounts can return up to ten connected social accounts
for a brand. Publishing tools require the account's publishing entitlement.
Generations
There is no cap on how many generations you may run. The limit is your credit balance.
Video analysis
advibly_analyze_video is free of credits but rate-limited, and direct HTTPS
video input is capped at roughly 18 MiB per video. Larger sources should be
hosted somewhere the analyser can stream them.
Uploads
| Input path | Limit or constraint |
|---|---|
| Presigned image upload | Up to 25 MiB |
| Presigned video upload | Up to 200 MiB |
Inline data_base64 | Small images only; hard cap 8 MiB and practical client limits may be lower |
Public source_url | The server must be able to fetch the URL without interactive authentication |
For a local file, use advibly_create_upload_url, upload the exact bytes with
HTTP PUT, then register its returned upload_key with
advibly_upload_asset. The signed size_bytes must match the uploaded body.
Credits
No expiry, no reset, no cap on how many you may hold.
Use advibly_check_credits for the live balance. A low balance limits billable
generation but does not block read-only account, brand, project, or library
calls.