Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

get-page-html

Retrieve HTML content from web pages using AdsPower browser automation, enabling data extraction and page analysis for browser profile management.

Instructions

Get the html content of the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get-page-html' tool. Checks browser connection and retrieves the full HTML content of the current page using Puppeteer's page.content() method.
    async getPageHtml() {
        browser.checkConnected();
        const html = await browser.pageInstance!.content();
        return html;
    },
  • Registers the 'get-page-html' tool with the MCP server, specifying its name, description, empty input schema, and wrapped handler.
    server.tool('get-page-html', 'Get the html content of the page', schemas.emptySchema.shape,
        wrapHandler(automationHandlers.getPageHtml));
  • Defines the empty input schema used for the 'get-page-html' tool, indicating no parameters are required.
    emptySchema: z.object({}).strict(),
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose whether this requires specific page states (e.g., loaded page), authentication, rate limits, or what happens with errors. The description is too vague for a mutation-free tool with zero annotation coverage.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't address behavioral aspects like what 'page' refers to (current page? specified page?), potential errors, or output format details, leaving gaps for the agent.

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

Parameters4/5

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

The tool has zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 reflects that the description doesn't need to compensate for any parameter gaps.

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 clearly states the action ('Get') and resource ('html content of the page'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-page-visible-text' or 'screenshot' that also retrieve page content in different formats, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring an open browser/page), exclusions, or comparisons to siblings like 'get-page-visible-text' for text-only retrieval or 'screenshot' for visual capture.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AdsPower/local-api-mcp-typescript'

If you have feedback or need assistance with the MCP directory API, please join our Discord server