FoxMCP

Overview Schema Source Related Servers Discussions Admin

tabs_move

Reorder browser tabs within a window or gather them into another window by ID. Use it to group tabs from one site together, and check the "Moved n of m" result since some moves are declined.

Instructions

Move tabs to a new position, optionally into another window

Reorders tabs within their window, or gathers them into a different window — to collect every tab for one site into a window of its own, create the window with create_window and pass its ID here.

Succeeding partially is normal, so check the result: it reads "Moved {n} of {m}", and a tab missing from the list did not move. Firefox declines some moves without raising an error, and the common one is that an unpinned tab cannot be placed in front of a pinned tab — with 3 pinned tabs, the lowest index an unpinned tab can reach is 3, and asking for 0, 1 or 2 moves nothing. Use tabs_list to see which tabs are pinned and what index each tab currently holds. A pinned tab can be moved to index 0 freely.

Moving between windows requires both to be normal windows, not popups, and either both private or both non-private.

profile_id is required: obtain it from profiles_list. All object IDs are local to that profile; never reuse them in another profile.

Input Schema

Name	Required	Description
`index`	No	Position to move to, counting from 0; -1 means the end (default: -1). An index inside a leading run of pinned tabs is refused for an unpinned tab — the move reports "No tabs moved" rather than failing.
`tab_ids`	Yes	Tab ID, or several as a list (`[12, 15]`) or a JSON string (`"[12, 15]"`). Listed tabs keep their given order at the destination.
`window_id`	No	Window to move the tabs into (optional, accepts int or string). Omit it to reorder within each tab's current window.
`profile_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Nov 1, 2026

TDQS

A4.9/5.0

Behavior5/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 so thoroughly: partial success is normal, the response reads "Moved {n} of {m}", Firefox silently declines some moves, the pinned-tab index rule is spelled out with a concrete example, cross-window moves require normal (non-popup) windows of matching private state, and profile_id must come from profiles_list with IDs local to that profile.

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?

Front-loaded with the one-line purpose, then layered constraints in short paragraphs under six lines each. Every sentence — pinned-tab rule, window-type rule, profile_id rule — carries an actionable constraint, so nothing reads as padding.

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?

An output schema exists so return-shape detail is not required, yet the description still explains the meaningful part of the result ("Moved {n} of {m}") and how to detect a failed move. For a 4-parameter mutation tool with cross-window side effects, the guidance on preconditions and partial failure is complete.

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?

Schema coverage is 75% and the description adds real meaning beyond it: the -1/end index convention implicit in reordering, the refusal of indices inside a leading pinned run, and order preservation for a tab_ids list. The index rule is partly duplicated from the schema text, but the cross-window and ordering semantics are genuine additions.

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 — move tabs to a new position, optionally across windows — in the very first line. It reads clearly distinct from siblings like tabs_list, tabs_create or create_window, which are referenced only as helpers.

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

Usage Guidelines5/5

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

Explicitly frames both modes (reorder within a window vs. gather into another window) and names the workflow prerequisite: create the target window with create_window and pass its ID. It also directs the agent to tabs_list when it needs pinned state or current indices.

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

Deploy Server