Skip to main content
Glama
Sign In

Bannerify

by io.github.bannerify
OverviewDiscussionsAdmin

Create PDF

create_pdf

Generate a PDF from a Bannerify template and return a link to the stored file. 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_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does usefully disclose that the result is a stored file returned as a link, but says nothing about permissions/scopes needed, whether a render counts against a quota, whether the render is synchronous, or what happens when a layer key does not match 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, both earning their place, with the outcome (link to stored file) front-loaded before the parameter hint. No filler or redundant restatement of the schema.

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?

For a two-parameter tool with full schema documentation and no output schema, the description covers purpose and return shape adequately. It is thin on the selection logic an agent needs when several Bannerify creation tools are available, and silent on failure modes of layer overrides.

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%, including detailed nested semantics for `modifications` (string vs object forms, per-layer field examples), so the schema already does the heavy lifting. The description's single clause about `modifications` adds nothing beyond it, making the baseline 3 correct.

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 a PDF from a Bannerify template and return a link to the stored file" gives a specific verb (generate) plus resource (PDF from a Bannerify template), which implicitly separates it from the create_image siblings. It stops short of naming an alternative explicitly, but the artifact type is unambiguous.

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

Usage Guidelines2/5

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

The only guidance is the mechanical instruction to pass layer overrides in `modifications`. There is no statement of when to reach for this versus create_image or create_image_from_shapes, no mention of required template access or any preconditions.

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