Skip to main content
Glama

ie_text

Read the visible text of a page, frame, or window to inspect rendered content without altering page behavior. Useful for extracting what a user actually sees.

Instructions

Get visible text of the page or of a specific frame.

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

Input Schema

NameRequiredDescriptionDefault
frameNoframe index or name (optional)
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

C2.7/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 and it does very little: it does not say whether the call waits for load, whether it fails on no session, what form the returned text takes, or how limit truncates results. The rich COM/tab behavioral caveats live in the schema's target parameter, not in the description.

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?

One short, front-loaded sentence with no filler. It is efficient, though the terseness is achieved partly by omitting information rather than by pruning redundancy.

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?

With no annotations and no output schema, the description should at minimum say what comes back (a text string), how 'visible' is determined, and what limit does. For a tool that operates across three distinct execution modes (driver, hwnd COM, tab), that is a meaningful gap.

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

Parameters2/5

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

Schema coverage is 67% and the target parameter already documents its own modes and constraints in detail. The description only restates the frame selection that the schema also covers, and says nothing about the undocumented 'limit' parameter or how frame index vs name is interpreted.

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 visible text') plus scope ('of the page or of a specific frame'), which distinguishes it from source-oriented siblings like ie_html. It stops short of naming a sibling alternative, so it is clear but not fully differentiated.

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 indication of when to prefer this over ie_html, ie_get or ie_wait_text, and no mention of prerequisites such as the page being loaded or the session being attached. The only usage signal is the implied page-vs-frame choice.

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