Skip to main content
Glama
Sign In

Bannerify

by io.github.bannerify
OverviewDiscussionsAdmin

Create image

create_image

Generate an image from a Bannerify template and return it inline. Pass layer overrides in modifications.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "templateId": "<templateId>"
    },
    "name": "create_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format. Defaults to png.
templateIdYesThe template id, for example tpl_abc123
modificationsNoLayer overrides keyed by layer name. A string replaces the layer text, e.g. {"headline":"Summer sale"}. An object sets layer specific fields, e.g. {"photo":{"src":"https://example.com/a.png"}}, {"qr":{"qrcode":"https://example.com"}}, {"table":{"rows":[["A","B"]]}}, {"tag":{"visible":false}}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the return channel ("return it inline"), which is real behavior beyond the schema, but it says nothing about permissions, rate limits, generation latency, or what happens when a layer name is not found in the template.

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?

Two short sentences, zero filler, with the core action and return behavior front-loaded and the parameter hint last.

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

Completeness3/5

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

The rich schema covers the three parameters and the inline return is stated, but with no annotations and no output schema the description leaves open error behavior for bad template IDs or unknown layer keys, and whether returned images are subject to size or format constraints.

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 description coverage is 100% and the modifications parameter is documented in detail in the schema itself, including string-vs-object override semantics. The description only restates that overrides go in `modifications`, adding no meaning beyond the structured data, so baseline 3 applies.

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

Purpose4/5

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

"Generate an image from a Bannerify template and return it inline" gives a specific verb (generate) and resource (image), and the phrase "from a Bannerify template" implicitly separates it from create_image_from_shapes. It never names that sibling, though, so the agent must infer which generation path to take.

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

Usage Guidelines3/5

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

Usage is only implied through the template-based framing and the required templateId; there is no explicit statement of when to prefer this over create_image_from_shapes or create_pdf, and no prerequisites are given.

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

All Bannerify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources