Skip to main content
Glama
AgentExtract MCP

AgentExtract MCP

extract_tables

Extract all HTML tables from a web page as structured 2D arrays and Markdown tables, making financial, pricing, and other tabular datasets ready for AI agents to parse and analyze.

Instructions

Extracts all HTML tables from a web page as structured 2D arrays and Markdown tables. Ideal for financial, pricing, and tabular datasets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "extract_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe absolute URL of the web page to extract tables from.
apiKeyNoOptional API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It discloses the return shape (2D arrays and Markdown) but says nothing about authentication (the apiKey parameter's effect), rate limits, handling of JS-rendered or nested tables, or what happens when a page has no tables.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler; the core capability and output format are front-loaded ahead of the use-case hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with full schema coverage and no output schema, the definition covers purpose, output shape, and a use case. The remaining gaps (empty-result behavior, dynamic page handling, auth role) are minor but non-trivial for a web-scraping tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both `url` and `apiKey` documented in the schema, so the baseline is 3. The description adds no extra meaning about URL constraints, redirects, or when the optional API key is actually needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Extracts all HTML tables from a web page') plus the output shape ('structured 2D arrays and Markdown tables'). That inherently separates it from extract_clean_markdown, but it never names or explicitly contrasts with the sibling, so differentiation is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Ideal for financial, pricing, and tabular datasets' gives a when-to-use cue, but there is no when-not guidance, no named alternative (e.g., extract_clean_markdown for general page text), and no note on when table extraction will fail or return nothing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.