Vizzy — Arabic AI Creative Platform

create_design

Generate a social media image or marketing design using AI. Optimized for Arabic text and Egyptian/Arab market aesthetics. Brand identity (colors, logo, style) from the user's Vizzy profile is automatically applied. Returns a public image URL. Costs 160 credits.

Input Schema

TableJSON Schema

Name	Required	Description
`style`	No	Visual style of the design
`topic`	Yes	What the design is about — in Arabic or English (e.g. 'بوست عيد الفطر لمطعم', 'Eid sale for a coffee brand')
`language`	No	Text language on the design. Default: arabic
`platform`	No	Target social media platform (affects dimensions and style)
`aspect_ratio`	No	Image dimensions — square (1:1), portrait (4:5), landscape (16:9), wide (2:1)
`extra_instructions`	No	Additional design guidance (e.g. 'خلفية ذهبية، نص أبيض، احتفالي')

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the transparency burden. It discloses key behaviors: automatic application of brand identity from Vizzy profile, return of a public image URL, and a cost of 160 credits. This adds meaningful context beyond the basic function, though it does not detail potential failure modes or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, each adding distinct value: function, target market, brand behavior, and output/cost. No filler or redundancy; all information is essential and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters and no output schema, the description covers the key context: output format (public URL), cost, and branding behavior. It does not explain return structure or error handling, but for a generation tool this is adequate, especially with full schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already well-documented. The description adds context about brand identity and market aesthetics but does not elaborate on individual parameter semantics beyond what the schema provides, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Generate a social media image or marketing design using AI.' It also specifies the target niche (Arabic text, Egyptian/Arab aesthetics) and distinct output (public image URL), differentiating it from sibling tools like generate_video or generate_music.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use this tool: for social media/marketing images with Arabic text and Egyptian/Arab market aesthetics. It does not explicitly mention alternatives or exclusions, but the context is sufficient for an agent to infer appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vizzy — Arabic AI Creative Platform tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clear, distinct purposes: content generation (create_design, generate_document, generate_music, generate_video), strategic planning (ads_analysis, marketing_ideas, media_spending), and social media content (linkedin_post, youtube_ideas, write_copy). Slight overlap exists between 'write_copy' and 'linkedin_post' (both text) and 'ads_analysis' vs 'marketing_ideas', but descriptions clarify the scope.

Naming Consistency3/5

The naming convention is mixed: some tools use verb_noun (create_design, generate_document, generate_video, write_copy), while others are noun_noun (ads_analysis, content_calendar, linkedin_post, marketing_ideas) or a bare verb (suggest). This pattern is readable but not fully consistent.

Tool Count5/5

With 13 tools, the platform covers a broad set of creative and marketing functions without feeling bloated. Each tool addresses a different content type or strategy aspect, and the count is appropriate for the stated purpose.

Completeness5/5

The tool surface covers the full lifecycle of a marketing campaign, from strategy (ads_analysis, marketing_ideas, media_spending) to content creation (copy, design, video, music, documents) to social media distribution (LinkedIn, YouTube, post ideas). Minor gaps like social media scheduling or advanced image editing exist but are not critical for the core creative workflow.

Resources

Need Help?