OGForge
Server Details
Free Open Graph image generator API. Create beautiful OG images with customizable themes, icons, and colors. No API keys required.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
2 toolsgenerate_og_imageCInspect
Generate an Open Graph image with customizable title, subtitle, theme, icon, and brand colors
| Name | Required | Description | Default |
|---|---|---|---|
| icon | No | Emoji or Lucide icon shortcode (e.g. "rocket", "heart") | |
| size | No | Size preset: og (1200x630), square (1080x1080), twitter-banner (1500x500), twitter-summary (800x418), linkedin (1200x627), instagram-story (1080x1920), facebook-cover (820x312) | |
| brand | No | Brand text shown at bottom (default: ogforge.dev) | |
| theme | No | Visual theme (default: dark) | |
| title | Yes | Main title text (required, max 200 chars) | |
| value | No | Prominent number/stat for metric layout (e.g. "2.4M", "99.9%"). Required when layout=metric | |
| width | No | Custom width in px (200-2400) | |
| accent | No | Accent color as 6-char hex without # (e.g. ff00aa) | |
| border | No | Border color as 6-char hex without # (e.g., ff00aa). Adds a frame around the image | |
| format | No | Output format: png (default), svg, webp (smallest), jpeg | |
| height | No | Custom height in px (200-2400) | |
| layout | No | Layout type: standard (default) or metric (KPI/stat card with prominent value) | |
| bgColor | No | Custom background color as 6-char hex without # (e.g. 1a1a2e). Overrides theme background | |
| caption | No | Small tagline/footer text below subtitle (max 100 chars). Useful for branding, attribution, or URLs. | |
| pattern | No | Background pattern overlay (default: none). Adds subtle texture to the image. | |
| subtitle | No | Subtitle text (max 300 chars) | |
| titleColor | No | Custom title text color as 6-char hex without # (e.g. ffffff). Overrides theme title color | |
| borderWidth | No | Border width in pixels (1-10, default: 3). Uses theme accent if border color not set | |
| gradientEnd | No | Gradient end color as 6-char hex without # (e.g. 0000ff). Requires gradientStart | |
| gradientAngle | No | Gradient direction in degrees 0-360 (default: 135). Also applies to theme gradients | |
| gradientStart | No | Gradient start color as 6-char hex without # (e.g. ff00aa). Requires gradientEnd | |
| subtitleColor | No | Custom subtitle text color as 6-char hex without # (e.g. cccccc). Overrides theme subtitle color |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. States it generates an image but omits critical behavioral details: persistence (file vs buffer), side effects, rate limits, parameter dependencies (gradientStart requires gradientEnd), and output return type. With 22 parameters and layout variations, this is insufficient disclosure.
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?
Single 12-word sentence with no waste. Front-loaded with verb. However, for a tool with 22 parameters and complex interactions (gradient pairs, layout dependencies), extreme brevity may underspecify. Appropriately concise but could benefit from second sentence on output or prerequisites.
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?
Given 100% schema coverage, description doesn't need to exhaustively document parameters. However, with no output schema, no annotations, and complex parameter interactions (metric layout requiring value, gradient pairs), the description should disclose output type and critical constraints. Relies too heavily on schema alone.
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?
Schema has 100% description coverage, establishing baseline 3. Description mentions 5 customizable fields but doesn't clarify semantics beyond schema (e.g., distinction between 'brand' text vs color fields, or size preset behavior vs custom dimensions). Adds minimal explanatory value over structured schema.
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?
Clear specific verb (Generate) and resource (Open Graph image). Lists customizable aspects (title, subtitle, theme, icon, brand colors). However, lacks differentiation from sibling tool 'list_themes' and doesn't specify scope (e.g., social media previews).
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?
Provides no guidance on when to use this tool versus others, when to call list_themes first to preview themes, or prerequisites like requiring 'value' parameter for metric layout. No explicit when/when-not rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_themesBInspect
List all available OG image themes
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Zero annotations provided, forcing description to carry full behavioral burden. While 'List' implies read-only, the description omits return structure, theme object properties, or pagination behavior. Does not confirm idempotency or safety guarantees.
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?
Single efficient sentence with zero redundancy. Front-loaded structure places action verb first. Appropriate length for zero-parameter listing utility.
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?
Adequate for a simple parameterless tool, identifying the resource domain (OG image themes). However, lacking output schema, the description should specify return value structure (array of theme objects) to be complete. Omits relationship to sibling generation tool.
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?
Input schema contains zero parameters. Per evaluation rules, zero-parameter tools receive baseline score of 4. Schema coverage is 100% (vacuously true), requiring no compensatory description.
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?
Clear verb 'List' and specific resource 'OG image themes'. Scope 'all available' is defined. Distinguishes from sibling generate_og_image by function (listing vs. generation), though explicit differentiation is absent.
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?
Provides no guidance on when to invoke this tool relative to generate_og_image or other alternatives. No mention of typical workflow (e.g., calling this before generation to select a theme).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!