SmartconversionAPI
Server Details
conversion image to webp/avif with 0.001 USDC and 0.0005 after 1000 requete
- Status
- Unhealthy
- 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
Average 3.9/5 across 6 of 6 tools scored.
Most tools have distinct purposes (compress, convert batch, convert to WebP, crop, get metadata, resize), but convert_image_to_webp and convert_batch could cause some confusion as both involve conversion, though the batch tool is clearly for multiple images. Descriptions help clarify the differences, but there is minor overlap in the conversion domain.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., compress_image, convert_batch, crop_image). The naming is predictable and uniform across all six tools, making it easy for agents to understand and use them without confusion.
With 6 tools, the server is well-scoped for image processing tasks. Each tool serves a specific function (compression, conversion, cropping, metadata extraction, resizing), and the count is appropriate for the domain, avoiding bloat while covering essential operations.
The toolset covers core image processing operations (compress, convert, crop, resize, metadata) with a free metadata tool and paid transformations. Minor gaps exist, such as no explicit tools for rotation, filtering, or format conversion beyond WebP/AVIF, but agents can likely work around these with the provided tools for basic workflows.
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!