Creative Claw

Use the Creative Claw MCP server as a media workspace: source durable assets, apply a brand theme, choose a model by capability, generate or process media, and save results for reuse.

Operating rules

1. Inspect before generating. Use search_assets for likely reusable media and get_theme for branded work.
2. Discover models at runtime. Call list_models for the modality, choose by capability, then call get_model_params before using model-specific fields. The reference tables are recommendations, not a substitute for runtime schemas.
3. Use durable references. Read references/platform-upload.md before importing attached or local media. Pass Creative Claw URLs to generation and processing tools.
4. Keep exact control syntax intact. Set agentic_prompting: false for complete prompts containing reference tokens, exact dialogue, timecodes, or strict layout/shot instructions. Leave it enabled for short, loose requests that benefit from rewriting.
5. Respect cost and approval boundaries. Explain the selected model and material settings before an expensive batch, long clip, or multi-shot production. Use exposed credit tools when available.
6. Treat queued work as unfinished. The inline viewer may monitor a generation for the user. Call check_job when another tool needs the completed URL, or when no viewer is monitoring the job. Never claim completion from a job ID alone.
7. Organize outputs. Give assets meaningful metadata when the tool supports it; otherwise use update_asset after completion. Use stable tags across a project.
8. Do not invent tools or parameters. If a tool is absent on the current client, follow references/platform-client.md. If a field is not in get_model_params, do not send it.
9. Capture actionable feedback. Use submit_feedback for bugs, missing features or models, confusing flows, generation-quality problems, and explicit praise. Read references/workflows/feedback.md before reporting.
10. Match the user's language. Conduct the workflow in the user's language, preserve supplied scripts and visible copy exactly, and verify the selected model supports the requested spoken or rendered language.
11. Use examples deliberately. Route requests for examples, inspiration, styles, or a close starting point to creativeclaw-find-examples. Do not search the catalog before every generation.
12. Keep HTML rendering explicit. Use creativeclaw-render-html-image or creativeclaw-render-html-video only when the user explicitly requests HTML/CSS, HyperFrames, code-driven rendering, or accepts that proposed method. Ordinary image or video requests stay with the generative skills.