Add text to a GIMP image by creating a text layer. Position the text at specific x,y coordinates and customize font, size, color, and border.
Create a text layer in an image.
| Name | Required | Description | Default |
|---|---|---|---|
| image_id | Yes | ||
| drawable_id | No | Optional drawable for floating text selection; omit for a new text layer. | |
| text | Yes | ||
| x | Yes | ||
| y | Yes | ||
| size | No | ||
| font | No | Sans-serif | |
| color | No | CSS color string, [r,g,b], [r,g,b,a], or {r,g,b,a}. | |
| border | No | ||
| antialias | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description does not disclose any behavioral traits (e.g., mutability, side effects, error behavior). It fails to inform the agent about what happens when creating a text layer.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no waste, but it lacks necessary detail. Conciseness here compromises completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 10 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain return values, how the text layer is created, or how parameters interact.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is only 20%, yet the tool description adds no parameter meanings. Most parameters are left unexplained, which is insufficient for an agent to invoke correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Create' and resource 'text layer' with context 'in an image', clearly distinguishing it from sibling tools like gimp.fill_rect or gimp.draw_polyline.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, or any prerequisites. The description is too minimal to provide usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/abelduarte/gimp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server