image-gen3-google-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Gemini API key for authenticating with Google's Gemini API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imagesB | Generate images using Google Gemini AI |
| create_image_htmlB | Create HTML img tags from image file paths |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Each tool targets a completely different operation: generate_images creates new images via AI, while create_image_html outputs HTML for existing image files. There is no ambiguity or overlap between them.
Both tools follow a clear verb_noun pattern in snake_case. 'generate_images' and 'create_image_html' use consistent styling and predictable naming conventions.
Only 2 tools for an image generation service is borderline. While the core functionality (generation and HTML output) is covered, the small number suggests a limited scope that may require additional tools for a complete workflow.
The tool set is notably incomplete: it lacks tools for listing, deleting, or managing generated images, and there is no way to configure generation parameters beyond what might be in the description. Users are left with a generation-and-output loop without lifecycle management.