Orshot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORSHOT_API_KEY | Yes | Your Orshot API Key used to authenticate with the image, PDF, and video generation API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-image-from-libraryB | Generate an image from an Orshot library template using specified modifications |
| generate-image-from-studioB | Generate an image from an Orshot Studio template using specified data modifications. Automatically maps URLs to appropriate image fields in the template. You can use either the template ID (numeric) or template name. |
| generate-imageB | Generate an image from an Orshot template (automatically detects library vs studio template). For studio templates, automatically maps URLs to appropriate image fields and supports template names. |
| get-library-templatesB | Get all available library templates for the user using their API key |
| get-studio-templatesC | Get all available studio templates for the user using their API key |
| get-template-modificationsB | Get available modifications for a specific template (works for both library and studio templates). For studio templates, you can use either ID or name. |
| check-api-statusA | Check the API connectivity and validate the API key |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Multiple tools have overlapping purposes that could cause confusion. The 'generate-image' tool claims to automatically detect library vs studio templates, making 'generate-image-from-library' and 'generate-image-from-studio' redundant. Additionally, 'get-library-templates' and 'get-studio-templates' are clearly distinct, but the generation tools create ambiguity in selection.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'check-api-status', 'generate-image-from-library'). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 7 tools, the count is reasonable for an image generation API server. It covers core functionalities like status checks, template retrieval, and image generation, though the redundancy in generation tools slightly bloats the set without adding clear value.
The tool set provides good coverage for the Orshot image generation domain, including API validation, template listing, modification options, and image generation. A minor gap exists in lacking tools for managing or deleting generated images, but core workflows are well-supported.