Skip to main content
Glama
Sign In
chat-export-server

chat-export-server

by svergio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tabs_ensure

Open or reuse a provider start tab in the bound browser without sending a prompt; use it before listing chats or asking when no platform tab is open.

Instructions

Open or reuse a provider start tab in the bound browser without sending a prompt. Prefer before chats_list/chat_ask when no platform tab is open; returns tab meta and created=true if chrome.tabs.create ran. Requires browsers_bind.

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": {
      "platform": "<platform>"
    },
    "name": "tabs_ensure"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdNoPrefer a tab whose URL already contains this chatId when matching open tabs
platformYesProvider id: chatgpt | grok | grok-x | claude | copilot | qwen | deepseek | perplexity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag write-adjacent, open-world, non-idempotent behavior; the description adds real context beyond them — that no prompt is sent, that chrome.tabs.create may run, and that created=true signals actual tab creation. It stops short of explaining what happens on reuse (e.g. focus/activation) or failure modes, so it is strong but not exhaustive.

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?

Three tight sentences with the action front-loaded and no filler. Slightly dense with abbreviations (chats_list/chat_ask, 'tab meta'), but every clause contributes.

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?

For a two-parameter, no-output-schema tool this is complete: action, routing condition, prerequisite, and return indicator (tab meta, created flag) are all covered. Nothing needed to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, with both platform (enum) and chatId documented in the schema text, so the description carries little burden here. The description implies the platform concept via 'provider start tab' but adds no matching or fallback nuance beyond what the schema already states for chatId.

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 pair and resource: 'Open or reuse a provider start tab in the bound browser'. It also disambiguates from the sibling chat tools by declaring 'without sending a prompt', so an agent knows this is not chat_ask.

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?

Gives an explicit routing rule: 'Prefer before chats_list/chat_ask when no platform tab is open', naming the alternatives and the condition that selects them. It also states the prerequisite 'Requires browsers_bind', covering the setup path.

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