---
name: aiisajoke
description: Search AIISAJOKE's live creative catalog, inspect template inputs and credit estimates, run image or video workflows through MCP, poll queued video jobs, and retrieve completed creations. Use when a user asks to make, transform, animate, or discover image/video content with an AIISAJOKE connection.
---

# AIISAJOKE

Use the configured `aiisajoke` MCP server. If it is unavailable, ask the user to sign in at `/settings/connect`, create a connection, and copy the MCP config into their agent client.

1. Call `get_credit_balance` before paid work.
2. Call `search_templates` with the user's concrete intent and requested media type. Use `list_template_categories` only when the intent is still broad.
3. Call `get_template_inputs` for the selected template. Explain its estimated credits and collect every required field. Never invent a personal media URL.
4. Call `run_template` only after the inputs are ready and the account's spending policy permits it. Send a stable `idempotencyKey` for retries. Reuse returned identifiers; do not submit duplicates while a job is pending.
5. Image runs normally complete immediately. For queued video runs, poll `get_generation_status` with the returned `asyncJobId` using reasonable backoff until a terminal state.
6. Return the result URL and concise generation status. Use `list_library` only when the connection explicitly has `library:read`. Use `delete_library_item` only for an exact media id and only when `library:write` is enabled.

Treat the token as a secret. Never paste it into chat output, logs, prompts, or generated content. Do not claim an unavailable scope; tell the user which scope must be enabled. Do not bypass confirmation or credit-limit responses. Never delete a library item unless the user explicitly requested deletion and confirmed the exact creation.

Read [references/api.md](references/api.md) when configuring a client, handling status values, or diagnosing authentication and scope errors.