Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_edge_og_svg_generator

Render Open Graph cards as SVG with custom title, subtitle, colors, theme, and dimensions for social previews and link sharing.

Instructions

[Dynamic Media] Render an Open Graph card (default 1200x630) as SVG Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": {
      "title": "<title>"
    },
    "name": "caelara_media_edge_og_svg_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (hex, with or without #)
fgNoText color (hex, with or without #)
brandNoBrand label
themeNodark (default) or light
titleYesHeadline
widthNoWidth in px (200-4000, default 1200)
accentNoAccent color (hex, with or without #)
formatNojson (default, includes svg + data URI) or svg (raw image/svg+xml)
heightNoHeight in px (200-4000, default 630)
subtitleNoSupporting line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/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 usefully discloses that the call goes to https://media.caelaralabs.com and gives measured latency (p50 12 ms, p95 42 ms), but it says nothing about authentication, rate limits, failure modes, or whether rendering is cached or stateless.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose and default size. The benchmark citation is somewhat tangential to invocation but is compact and dated, so it earns marginal keep.

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 ten-parameter generator the schema covers inputs well and the format parameter implies the return shape, so the description need not explain outputs. However, with zero annotations the description should say more about external-service behavior (auth, limits, error handling) to be fully sufficient.

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%, with every one of the ten parameters documented including ranges (200-4000 px) and formats (hex with or without #). The description adds only the default dimensions, which the schema already states, so the 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?

The description gives a specific verb and resource: 'Render an Open Graph card ... as SVG', plus the default 1200x630 canvas. It is clear what the tool produces, but it never contrasts itself with close siblings such as caelara_media_dynamic_social_card_composite, so an agent must infer which one to pick.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only implied context is 'Open Graph card', leaving the agent to guess how this differs from the social-card composite sibling.

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

Deploy Server

Other Tools