Skip to main content
Glama

Vizzy — Arabic AI Creative Platform

by space.vizzy.api

write_copy

Write Arabic marketing copy, social media captions, or ad text. Uses Egyptian dialect by default — professional, relatable, culturally relevant to the Arab market. Returns copy text and hashtags. Costs 80 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesWhat to write about (e.g. 'عرض رمضان لمطعم كوفي', 'summer sale for a fashion brand')
languageNoLanguage — arabic uses Egyptian dialect (عامية مصرية) by default
platformNoTarget platform (affects copy length and tone)
extra_instructionsNoTone, audience, special requirements (e.g. 'فكاهي وخفيف', 'urgent, expires tonight')

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the default dialect, tone, output format (copy text and hashtags), and cost (80 credits), providing valuable context beyond the schema.

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 only two sentences, front-loaded with the core purpose and followed by behavioral details and cost. Every sentence carries essential information with no redundancy.

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 no output schema and no annotations, the description compensates by stating return values (copy text and hashtags), cost, and default dialect. It is sufficiently complete for a generation tool, though it could briefly mention how the 'english' language option differs, which is a minor gap.

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?

The schema already describes all four parameters with full coverage, including the platform's effect on length/tone. The description adds minimal new parameter semantics, only confirming the Egyptian dialect default already in the schema. With 100% schema coverage, baseline 3 is appropriate.

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 uses a specific verb ('Write') and identifies the resource ('Arabic marketing copy, social media captions, or ad text'), clearly stating the tool's function. It distinguishes itself from sibling tools by highlighting the Egyptian dialect and cultural relevance to the Arab market, making it unique among copy-related tools.

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 clearly implies when to use this tool: for Arabic marketing copy, social captions, or ad text. It provides context about the default dialect and cultural fit, but does not explicitly mention when not to use it or name alternative tools, so it lacks explicit exclusions.

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 toolsInspect
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