AgentRender
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTRENDER_API_KEY | Yes | Your AgentRender API key (Bearer token) from https://agentrenderapi.com. Required to authenticate requests. | |
| AGENTRENDER_BASE_URL | No | API base URL for AgentRender. | https://api.agentrenderapi.com |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshotC | Capture a public URL as an image (PNG/JPEG/WebP). Returns JSON with image_base64 + receipt. |
| pdfB | Capture a public URL as a PDF. Returns JSON with pdf_base64 + receipt. |
| extractB | Extract title, meta description, canonical, main text, and links from a URL (non-LLM). |
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 3 tools
Each tool captures a distinct output format from a URL: PDF, image, or extracted text/metadata. There is no overlap in purpose, so an agent can easily select the correct tool without ambiguity.
All tool names are single, lowercase verbs describing the action ('pdf', 'extract', 'screenshot'). While not verb_noun, the pattern is perfectly consistent and intuitive.
With 3 tools covering URL rendering to PDF, image, and text extraction, the count is well-scoped for a focused utility server. Each tool serves a clear purpose without bloat.
The set covers the primary content-capture needs (PDF, image, text extraction). Missing minor capabilities like full HTML or raw response capture, but the core workflows for a render/capture service are complete.