Skip to main content
Glama
Sign In
oh-my-mcp

oh-my-mcp

by quyansiyuanwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

parse_html

Extract specific elements from HTML content using CSS selectors for precise data retrieval.

Instructions

Parse HTML and extract elements using CSS selector.

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": {
      "html": "<html>",
      "selector": "<selector>"
    },
    "name": "parse_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesHTML content to parse
selectorYesCSS selector to find elements

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not mention error behavior (e.g., invalid CSS, malformed HTML), output format, or any side effects. Minimal context is given.

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?

Extremely concise, a single sentence that front-loads the purpose. It wastes no words, though it could be slightly more informative without losing brevity.

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

Completeness3/5

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

For a simple tool with an output schema, the description is minimally adequate. It does not explain the return structure or edge cases, but given low complexity, it meets basic needs.

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%, so the schema already documents both parameters. The description adds no extra meaning beyond restating the parameter purpose; baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (parse/extract), resource (HTML), and method (CSS selector). It distinguishes from sibling tools like parse_csv or parse_json, making its purpose unambiguous.

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?

Usage is implied: use when you need to extract elements from HTML via CSS selectors. However, no explicit guidance on when not to use it or alternatives (e.g., fetch_webpage for fetching, browser_get_text for visible text) is provided.

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