Skip to main content
Glama
Sign In
termux-puppeteer-mcp

termux-puppeteer-mcp

by kevintpeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_session

Create a new browser session for multi-step workflows, returning a sessionId that persists state across calls. Sessions auto-expire after 5 minutes of inactivity.

Instructions

Create a new browser session for multi-step workflows. Returns a sessionId that persists state between calls. Sessions auto-expire after 5 minutes of inactivity.

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

Input Schema

NameRequiredDescriptionDefault
metadataNoOptional metadata to attach to the session (e.g., agentId, purpose)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses creation, sessionId return, state persistence, and auto-expiration. It does not mention resource consumption or the need to call close_session, but overall it is transparent about key behavioral traits.

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 concise sentences, front-loaded with the primary action. Every sentence adds value: creation, return value, and expiration. No unnecessary words.

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?

Given no output schema, the description explains the return value. It covers creation, persistence, and expiration. However, it does not address potential errors (e.g., session limit) or prerequisites, but for a simple tool, it is sufficiently complete.

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

Parameters5/5

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

The only parameter, 'metadata', is described as 'Optional metadata to attach to the session (e.g., agentId, purpose).' This adds meaningful examples beyond the schema description, enhancing understanding of its usage.

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: 'Create a new browser session for multi-step workflows.' This is a specific verb+resource combination that distinguishes it from sibling tools like close_session (destroys) and list_sessions (lists).

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

Usage Guidelines4/5

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

The description mentions 'multi-step workflows' and auto-expiration after 5 minutes, providing clear context for when to use the tool. However, it does not explicitly state when not to use it or name alternatives, though siblings provide indirect guidance.

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