Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

get_page_content

Retrieve HTML or text content from the current browser page or a specified tab so AI agents can inspect and extract page data.

Instructions

Get the HTML content or text of the current page

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
formatNoReturn HTML or text (default text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It establishes that this is a content retrieval operation and mentions HTML versus text, but it does not clarify whether the HTML is rendered DOM or raw source, whether it covers the whole document or visible content, how frames are handled, or any size or permission constraints.

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?

The description is a single front-loaded sentence with no wasted wording. Its brevity is effective structurally, even though the content is under-specified in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. However, it does not resolve the ambiguity between current page and optional tabId, nor does it help the agent choose between this and other page-inspection siblings.

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%, so the tabId and format parameters are already documented in the input schema, including the default of text. The description adds little beyond the schema by referring to the current page and choosing HTML or text, making the baseline 3 appropriate.

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 names a specific verb and resource: get HTML content or text of the current page. It is clear what the tool returns, though it does not explicitly distinguish itself from sibling retrieval tools such as get_accessibility_tree, take_snapshot, or get_response_body.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or named alternatives. An agent must infer from the sibling list whether this is preferable to take_snapshot, get_accessibility_tree, or get_current_tab, and no when-not or prerequisite conditions are stated.

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