Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

页面 HTML

get_page_html
Read-only

Retrieve the complete HTML of the current page in a browser tab, excluding iframe contents. Optionally truncate output to a specified maximum length for easier handling.

Instructions

获取标签页当前页面的完整 HTML（不含 iframe 内部内容），超长时截断。

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_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idNo标签页 id，省略时用最新标签页
max_charsNo返回 HTML 的最大字符数，超出部分截断

Output Schema

NameRequiredDescriptionDefault
urlNo
htmlYes
tab_idYes
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotation readOnlyHint=true already indicates safety. The description adds beneficial behavioral details: it excludes iframe content and truncates if exceeding max_chars, making side effects and output limits transparent. No contradictions.

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?

The description is a single, concise sentence with no unnecessary words. It directly states the action, the scope (excluding iframes), and the truncation rule. Perfectly structured.

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?

The description provides sufficient context for an agent to understand the return value (HTML string) and its limitations. No output schema is present, but the description covers the essential behavior. Minor missing details like error handling are not critical.

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?

Both parameters (tab_id and max_chars) have complete schema descriptions explaining their meaning and defaults. The description does not add extra semantic information beyond what the schema already provides, so the baseline of 3 applies.

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: to get the complete HTML of the current tab page, excluding iframe inner content, with truncation behavior. This is specific and distinct from sibling tools like get_page_info or run_js.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description does not mention when not to use it or compare it to other HTML-retrieval methods (e.g., run_js). The agent must infer usage from the name alone.

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