Skip to main content
Glama
Sign In
ia-cae-zurekin-mcp

ia-cae-zurekin-mcp

by luistorres789321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

extract_page_content

Extract structured content from a webpage, including tables and links, for data analysis or archiving. Solves the problem of retrieving clean, organized page content without manual scraping.

Instructions

Extrae el contenido estructurado de una p�gina.

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_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
include_tablesNo
include_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so the description bears full burden. It implies a read operation ('extracts') but does not disclose side effects, idempotency, error handling, or any behavioral traits. Insufficient for a tool with zero annotations.

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

Conciseness4/5

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

Single sentence, concise and front-loaded. No extraneous information. However, lacks structure (e.g., bullet points), but this does not detract from its brevity.

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

Completeness2/5

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

Given 3 parameters, no output schema, and no annotations, the description is too brief. Does not explain what 'structured content' means, how boolean parameters affect extraction, or the output format. Inadequate for effective agent usage.

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

Parameters1/5

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

Schema has 0% coverage (no property descriptions). The description does not explain what include_tables or include_links do, nor does it add any meaning beyond the schema. The description adds zero value for parameter understanding.

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?

The description clearly states the tool extracts structured content from a page, using a specific verb and resource. It distinguishes from siblings like get_page (likely raw content) and list_sections (sections), but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_page or list_sections. No context about prerequisites or scenarios where this tool is preferred.

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

Deploy Server

Other Tools