api_og_imageGenerate an Open Graph image 1200x630 from title/subtitle/theme. ?title=&subtitle=&theme=indigo|dark|green|red|blue [HTTP x402 price: $0.015]
| Name | Required | Description | Default |
|---|---|---|---|
| params | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / params / additionalPropertiesRemoved value: -trueInput schema / properties / params / propertiesAdded value: +{
+ "subtitle": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "theme": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ },
+ "title": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ }
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the fixed output size, theme options, and price, which is useful. However, it does not clarify the return type, error behavior, or whether title/subtitle are effectively required, which matters when all schema parameters are optional.
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 one dense, front-loaded sentence covering the action, output size, inputs, theme choices, and cost. Every piece of text earns its place, with no filler or repetition of the tool name.
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?
For a small tool this is mostly complete: it states the output, size, parameters, allowed themes, and price, and an output schema exists. The main gap is lack of guidance on required vs optional inputs and response behavior, which an agent needs to invoke it reliably.
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 description coverage is 0%, so the description must compensate. It does add meaning by listing valid theme values and identifying title/subtitle as content inputs. However, it does not explain optionality, text length limits, encoding needs, or what happens when required text params are omitted.
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 names a specific verb ('Generate'), a specific resource ('Open Graph image'), the exact dimensions (1200x630), and the input fields (title/subtitle/theme). This clearly differentiates it from the many sibling conversion and lookup tools.
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?
The description implies when to use the tool by stating what it produces, but it gives no explicit guidance about when to choose it over alternatives or when not to use it. For a simple single-purpose utility this is adequate, though not exemplary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have unclear boundaries: api_search and api_serp_google both return Google results, api_scrape and api_render_text both extract page text, and api_hash_multi overlaps with api_sha256 for SHA-256/SHA-512. While many tools are distinct, these overlapping pairs create real misselection risk.
Every tool follows the same api_<snake_case> pattern with no mixed conventions or casing styles. The prefix makes the server immediately recognizable and the action/resource is consistently readable across all 44 tools.
44 tools is well over the 25+ threshold for a well-scoped set, making the server feel like a grab-bag of unrelated utilities. Even though each tool is small and individually useful, the overall surface is too large and would benefit from consolidation into focused sub-servers.
The set covers many common utility categories—encodings, conversions, text analysis, web scraping, SEO, and trends—but has notable one-way gaps: CSV/YAML/TOML all convert to JSON but not back, and markdown converts to HTML but not the reverse. The broad domain makes full completeness hard to define, so only major reverse-conversion gaps stand out.