Skip to main content
Glama
Sign In
edge-mcp

edge-mcp

by hualang-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_tabs

Lists every open tab in Microsoft Edge with its targetId, URL, and title, enabling you to identify and manage active browser tabs.

Instructions

List all open tabs in Edge with their targetId, URL, and title.

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": "list_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/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. It does disclose the returned fields (targetId, URL, title), which is genuinely useful, but it says nothing about ordering, whether tabs across all windows are included, or whether a live browser session is required.

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?

A single front-loaded sentence with no filler. The action and the returned fields are both stated immediately, with nothing redundant.

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

Completeness4/5

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

For a zero-parameter read tool with no annotations or output schema, the description covers the essential contract: what is listed and what each entry contains. Minor gaps remain around tab ordering and multi-window scope, but nothing that would cause a misinvocation.

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 and the schema is an empty object, so there is nothing to disambiguate. The description correctly implies no input is needed, matching the baseline for a parameterless tool.

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 states a specific verb and resource ("List all open tabs in Edge") and even names the returned fields, which makes it clearly distinct from the mutation siblings new_tab, close_tab, and switch_tab. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating in so many words.

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?

There is no explicit when-to-use statement or exclusion, but the usage is strongly implied: enumerate tabs to obtain a targetId before calling switch_tab or close_tab. An agent can infer this, though the description never makes the handoff explicit.

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