Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

get_page_info

Extract details about the current webpage, including structure and content, through browser automation using Playwright on the AutoProbeMCP server.

Instructions

Get information about the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'get_page_info' tool that retrieves and returns the current page's title, URL, and viewport dimensions.
              case 'get_page_info': {
                if (!currentPage) {
                  throw new Error('No browser page available. Launch a browser first.');
                }
    
                const title = await currentPage.title();
                const url = currentPage.url();
                const viewport = currentPage.viewportSize();
    
                return {
                  content: [
                    {
                      type: 'text',
                      text: `Page Info:
    Title: ${title}
    URL: ${url}
    Viewport: ${viewport?.width}x${viewport?.height}`
                    }
                  ]
                };
              }
  • src/index.ts:314-321 (registration)
    Registration of the 'get_page_info' tool in the listTools response, including its name, description, and empty input schema.
    {
      name: 'get_page_info',
      description: 'Get information about the current page',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets information' but doesn't specify what information (e.g., title, URL, dimensions), whether it requires page load, or any side effects. This is inadequate for a tool with zero annotation coverage, leaving key behavioral traits unclear.

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 ('Get information about the current page') with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool's complexity (simple read operation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned (e.g., page title, URL, HTML), leaving the agent unsure of the tool's output. For a tool with no structured output documentation, more detail is needed.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as there's nothing to compensate for, and the description doesn't introduce confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get information about the current page'), which is clear but vague. It specifies a verb ('Get') and resource ('current page'), but doesn't distinguish what type of information is retrieved or how it differs from sibling tools like 'get_element_text' or 'analyze_screenshot'. The purpose is understandable but lacks specificity.

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. With siblings like 'get_element_text' (for specific elements) and 'analyze_screenshot' (for visual analysis), there's no indication of when 'get_page_info' is appropriate—e.g., for metadata, URL, or general page properties. Usage is implied only by the name, not explained.

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

Related 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/Wladastic/AutoProbeMCP'

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