Skip to main content
Glama
Sign In
Browser Control

Browser Control

by PrinceGarth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reorder-browser-tabs

Rearranges open browser tabs into a specified order, letting you organize Firefox tabs by a provided sequence.

Instructions

Change the order of open browser tabs

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": {
      "tabOrder": "<tabOrder>"
    },
    "name": "reorder-browser-tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabOrderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says almost nothing: not whether the reorder is destructive to pinned/grouped state, whether it requires a specific browser context, whether it fails, or how the result is reported. Only the implicit 'this mutates tab order' is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no waste, which is good structurally, but the brevity here reflects under-specification rather than discipline given the complete absence of parameter and behavior detail.

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?

For a mutation tool with no annotations, no output schema, and an undocumented required array parameter, the description is far too thin. An agent cannot reliably construct a valid tabOrder value from the definition alone.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds zero meaning for 'tabOrder'. It is an array of numbers with no indication whether the values are tab indices, tab IDs, or positions, nor whether the array must be a complete permutation of open tabs or only a subset.

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+resource ('Change the order of open browser tabs'), which clearly separates it from close-browser-tabs, open-browser-tab, and get-list-of-open-tabs. It does not, however, distinguish itself from group-browser-tabs, which also rearranges tabs, so sibling differentiation is incomplete.

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 guidance on when to use this versus group-browser-tabs or close-browser-tabs, no prerequisites, and no statement of what state the tabs must be in first. The agent must infer usage entirely from the name.

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