AgenticTotem Web Extractor
Server Details
AI web extraction: send URLs + a JSON Schema, get clean structured data. Pay-per-use via x402.
- Status
- Healthy
- 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 4.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and singular.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.
One tool is too few for a server named 'Web Extractor' that implies broader web-related functionality. A single extraction tool feels thin and under-scoped for the domain.
The tool surface is severely incomplete for web extraction. It lacks basic operations like listing or managing extraction jobs, validating schemas, or handling errors, which are essential for a robust extraction workflow.
Available Tools
1 toolweb_extractAInspect
Extract structured data from web pages. Send 1-10 URLs and a JSON Schema describing the data shape you want. Returns extracted data for each URL. Costs $0.01 USDC per URL via x402 or MPP.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | URLs to extract data from (http/https only) | |
| schema | Yes | JSON Schema with type "object" and properties describing desired output shape |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full disclosure burden. It successfully reveals the cost model ($0.01 USDC, payment methods) and return behavior ('Returns extracted data for each URL'). However, it omits safety characteristics (read-only vs destructive), error handling behavior, timeout policies, and failure modes (partial vs total failure) that would be essential for a production web extraction tool.
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?
Four sentences, zero waste: (1) purpose, (2) input spec, (3) output behavior, (4) cost model. Perfectly front-loaded with the core verb. Each sentence delivers distinct, non-redundant information without reciting schema details already covered in structured fields.
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 2-parameter tool with 100% schema coverage but no annotations or output schema, the description adequately compensates by disclosing return behavior and cost structure. The mention of 'Returns extracted data for each URL' partially addresses the missing output schema, though it could specify the return format structure (array vs object) more precisely.
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 coverage is 100%, establishing baseline 3. Description adds valuable semantic context beyond the schema: specifying that the schema parameter describes 'data shape you want' (clarifying its purpose) and reinforcing the URL quantity constraints ('1-10 URLs'). Elevates understanding above raw schema definitions.
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?
Description opens with specific verb 'Extract' and clear resource 'structured data from web pages'. Immediately communicates core function without ambiguity. No siblings exist requiring differentiation, but the purpose statement is precise and actionable.
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?
Provides concrete constraints ('1-10 URLs') and critical economic context ('Costs $0.01 USDC per URL via x402 or MPP') that inform invocation decisions. Lacks explicit 'when not to use' guidance, but the cost disclosure and batch size limits effectively guide usage patterns.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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!