AgentQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTQL_API_KEY | Yes | Your API key from the AgentQL Dev Portal |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract-web-dataA | Extracts structured data as JSON from a web page given a URL using a Natural Language description of the data. |
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 1 tool
With only one tool, there is no risk of confusion between tools, so disambiguation is perfect.
The single tool name 'extract-web-data' follows a clear verb_noun pattern, and consistency is trivially maintained.
A single tool is too few for a web scraping server, which typically requires tools for different actions (e.g., listing, configuring) or handling multiple extraction strategies.
The server only provides extraction via natural language, missing common features like pagination, multiple output formats, or error handling, leaving significant gaps for agents.