Skip to main content
Glama

Get page content

get_page_content
Read-only

Get the HTML content of the current page to answer the user's request about it. Use it only for websites and accounts that the user owns or is authorized to use, and follow their terms. Not for crawling or bulk data extraction from third-party websites.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession ID of the connected browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"ID de sesión del navegador conectado"New value: +"Session ID of the connected browser"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered; the description adds genuine non-annotation context about ownership, authorization, and terms-of-service compliance. It does not say whether the HTML is truncated, main-frame only, or how large pages are handled, which is the remaining behavioral gap.

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, front-loaded with the action and resource, with no redundant restatement of the title. The phrase "to answer the user's request about it" is slightly expendable but does frame intent.

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 one-parameter read tool with no output schema and full annotation coverage, the definition supplies purpose, authorization constraints, and scope exclusions. The only shortfall is that it never characterizes the returned HTML (size, truncation, frame scope), which matters for an open-world browser read.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains sessionId as the connected browser's session ID. The description adds no further meaning about session scoping or behavior when the session is stale, so the baseline of 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?

States a specific verb and resource ("Get the HTML content of the current page"), which cleanly separates it from siblings like get_elements, take_screenshot, or navigate_to_url that operate on the same browser session. It does not explicitly name an alternative, but the resource is unambiguous.

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?

Gives a clear when-not clause ("Not for crawling or bulk data extraction from third-party websites") plus an authorization precondition, which is stronger guidance than most read tools provide. It stops short of naming which sibling to use instead when the agent needs structured element data or a visual capture.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources