Skip to main content
Glama

ie_tabs

Lists visible IE-mode tabs in open Edge windows as JSON, including hwnd, title, URL, and attached status, so you can identify which tab to attach to.

Instructions

List the IE-mode tabs the user has open in Edge windows, as JSON: hwnd (give it to ie_attach), target ("tab:"), top_hwnd, pid, title, url and attached. Only the visible tab of each window is listed (activate the tab in the browser first). Windows of other ie-mcp sessions are never listed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return fields, the visibility-only limitation, the workaround for hidden tabs, and the session isolation rule that silently excludes other sessions' windows. The main omission is any note on cost, freshness, or whether the list is a snapshot.

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?

Three short sentences: purpose first, then the return contract with an actionable hint on hwnd, then the two exclusion rules. No filler, and every clause carries information the agent would otherwise have to discover by trial.

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

Completeness5/5

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

The tool has no parameters, no annotations, and no output schema; the description compensates by specifying the returned JSON fields and the visibility/session constraints, which is exactly what would otherwise be missing. Nothing needed to invoke it correctly is absent.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The field explanations it does provide describe the response, not inputs, which 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?

States a specific verb and resource ('List the IE-mode tabs ... open in Edge windows') and then enumerates the exact JSON fields returned, so the agent knows both the operation and the payload shape before calling. The scope constraints ('only the visible tab of each window', 'windows of other ie-mcp sessions are never listed') further distinguish this from sibling enumeration tools such as ie_browsers.

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

Usage Guidelines4/5

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

Gives explicit downstream routing ('hwnd (give it to ie_attach)') and a concrete prerequisite ('activate the tab in the browser first'), which tells the agent how to obtain data this tool won't return. It stops short of a full when-not statement or naming a contrasting sibling for the window-level case.

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