Skip to main content
Glama

get_page_info

Retrieve details about the currently open webpage, including URL, title, and metadata, to understand page context and support browsing automation.

Instructions

Get information about the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:314-321 (registration)
    Tool registration for 'get_page_info' in the ListToolsRequestSchema handler. Defines the tool name, description, and empty input schema (no parameters required).
    {
      name: 'get_page_info',
      description: 'Get information about the current page',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Handler implementation for 'get_page_info' tool. Checks if a browser page is available, then retrieves the page title, URL, and viewport size using playwright's Page API, returning them as formatted text.
              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}`
                    }
                  ]
                };
              }
Behavior2/5

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

No annotations exist, so the description carries full responsibility. It only states the purpose without disclosing behavioral traits such as whether the tool is read-only, its side effects, or the nature of the returned information. This is insufficient for a read operation.

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, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose, earning a top score for conciseness.

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?

The tool lacks an output schema and annotations, yet the description does not specify what information is returned (e.g., URL, title, HTML). This leaves the agent without sufficient context to understand the tool's output, making it incomplete.

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?

There are no parameters, and the schema coverage is 100% (empty schema). The description adds no parameter information, but with zero parameters, the baseline is 4, which is appropriate as the schema fully defines the input.

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 tool retrieves information about the current page, distinguishing it from other tools that perform actions or extract specific elements. However, it lacks specificity on what exact information is returned (e.g., URL, title, HTML), leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives like get_element_text or evaluate_javascript. The description does not include any when-to-use or when-not-to-use information.

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/Wladastic/mcp-browser-server'

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