Skip to main content
Glama

ie_html

Retrieves the HTML source of a page or specific frame, returning the document's normalized outerHTML when interacting over COM by window handle or attached tab.

Instructions

Get the HTML source of the page or of a specific frame. Over COM (target hwnd:/tab:) it is the document's outerHTML (no doctype, markup as the engine normalised it), not the original source the driver returns.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ie_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNo
limitNo
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does add real behavioral context: over COM the result is the document's outerHTML, lacks a doctype, and is engine-normalised markup rather than the original driver source. That is a meaningful fidelity caveat an agent could not infer from the schema. It omits any note on output size or truncation despite a limit parameter existing.

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?

Two sentences, front-loaded with the core action, and every clause adds information about return fidelity. The second sentence is dense with parentheticals but still readable; nothing is filler.

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 read tool with no output schema, the description does explain what is returned and how it differs between driver and COM modes. The gap is the undocumented limit parameter and no guidance on large documents, which matters for a tool that can return very large payloads.

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 only 33%, and only target has a schema description. The description reinforces target semantics (hwnd:/tab: meaning COM access) and explains frame indirectly via 'of a specific frame', but the limit parameter — the one governing output size — is left entirely unexplained in both schema and description.

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 ('Get the HTML source') plus scope ('of the page or of a specific frame'), which is more precise than a bare name restatement. It does not name a sibling to contrast with (e.g. ie_get for text/values), so the differentiation is implied rather than explicit.

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?

The mention of 'a specific frame' implies when to supply the frame parameter, and the COM note implies when target hwnd:/tab: applies. There is no explicit statement of when to prefer this over ie_js or ie_get, nor any exclusion guidance.

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