Skip to main content
Glama
Sign In
Tap

Tap

by LeonTing1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

tap_runtime

Idempotent

Switch browser runtime mid-session: headless for no-login, Chrome for real login sessions and write operations.

Instructions

Switch browser runtime mid-session. Default is headless (no login). Use 'chrome' when you need the user's real browser with login sessions (Xiaohongshu, Zhihu, etc.) or for write operations (publish, comment). Use 'headless' to switch back. (Unrelated to tap mcp connect, which registers the Tap MCP server with an AI host.)

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": {
      "runtime": "<runtime>"
    },
    "name": "tap_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
runtimeYeschrome = user's real Chrome browser (login sessions available). headless = Playwright (fast, no login).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.1
  2. Removedv0.27.0
  3. Addedv0.15.14
  4. Removedv0.15.8
  5. Addedv0.1.3

TDQS

A4.7/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds behavioral context: switching runtime affects login availability (chrome provides user sessions, headless does not). No contradictions with annotations.

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?

Two sentences, front-loaded with purpose, highly concise with no wasted words. Clearly structured and easy to parse.

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 simple runtime switch tool with no output schema, the description covers behavior, usage scenarios, and distinguishes from unrelated commands. No gaps.

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 single parameter has a clear enum and schema description. The tool description adds value by contextualizing when to use each value (chrome for login, headless otherwise), going beyond the schema.

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?

The description clearly states the tool's purpose: 'Switch browser runtime mid-session.' It specifies the two runtime options (chrome and headless) and what each is used for, making the action unambiguous.

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?

The description explicitly advises when to use each runtime: chrome for login sessions or write operations, headless to switch back. It also distinguishes from `tap mcp connect`, providing clear usage context.

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