Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_snapshot

Capture a structured snapshot of the current browser page—title, URL, headings, links/buttons, and truncated body text—so an agent can inspect content before choosing what to click.

Instructions

Return a structured snapshot of the current page: title, URL, headings, links/buttons with their text, and a truncated body. Use this as the agent's 'see the page' primitive before deciding what to click.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "tb_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyCharsNoHow many characters of body innerText to include (default 5000, max 50000).
sessionIdYesSession ID from tb_openBrowser

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the disclosure burden, and it does spell out the returned structure (including that the body is truncated), which is valuable given there is no output schema. However, it says nothing about side effects on the page, whether reads require an active browser state, or how dynamic content is handled.

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?

Two sentences: the first front-loads what is returned, the second states the usage rule. Nothing is wasted, though the quoted 'see the page' framing is decorative rather than informative.

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?

For a two-parameter read tool with no output schema and no annotations, the description covers both the action and the return contents well enough to invoke correctly. Minor gaps remain around page-state prerequisites and truncation side effects, but nothing essential 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 description coverage is 100%, with both sessionId and bodyChars documented in-schema including default and max. The description's phrase 'truncated body' loosely ties to bodyChars but adds no format or tuning guidance beyond the schema, so the baseline 3 applies.

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?

The description gives a specific verb ('Return a structured snapshot') and resource ('the current page'), then enumerates the contents: title, URL, headings, links/buttons with text, truncated body. That enumeration distinguishes it from text-only siblings like tb_getText and image-based tb_screenshot, though neither is named explicitly.

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?

It gives a clear usage rule: use this as the 'see the page' primitive before deciding what to click. It establishes the read-then-act ordering but states no exclusions or alternatives for cases where a screenshot or raw text extraction would be preferable.

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