Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

navigate

Direct a browser profile to a specific URL using AdsPower LocalAPI, enabling automated navigation for browser automation tasks.

Instructions

Navigate to the url

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe url to navigate to

Implementation Reference

  • The main handler function for the 'navigate' tool. It checks if the browser is connected, navigates the current page to the specified URL using Puppeteer, and returns a success message.
    async navigate({ url }: NavigateParams) {
        browser.checkConnected();
        await browser.pageInstance!.goto(url);
        return `Navigated to ${url} successfully`;
  • Zod schema defining the input parameters for the 'navigate' tool: an object with a required 'url' string field.
    navigateSchema: z.object({
        url: z.string().describe('The url to navigate to')
    }).strict(),
  • Registration of the 'navigate' tool on the MCP server, linking the name, description, input schema, and wrapped handler function.
    server.tool('navigate', 'Navigate to the url', schemas.navigateSchema.shape,
        wrapHandler(automationHandlers.navigate));
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a navigation action but doesn't specify if it requires an existing browser, what happens on failure (e.g., invalid URL), or any side effects like page loading. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with a single, direct sentence that front-loads the core action. There is no wasted verbiage, making it efficient and easy to parse, though this conciseness contributes to gaps in other dimensions.

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 complexity of browser navigation tools, lack of annotations, and no output schema, the description is incomplete. It fails to address key aspects like prerequisites, error handling, or return values, making it inadequate for safe and effective use by an AI agent.

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?

The input schema has 100% description coverage, with the 'url' parameter clearly documented. The description adds no additional meaning beyond what the schema provides, such as URL format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 'Navigate to the url' states the action (navigate) and target (url), but is vague about the context (e.g., browser navigation) and doesn't distinguish it from sibling tools like 'open-browser' or 'open-new-page'. It provides a basic purpose but lacks specificity and differentiation.

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 such as 'open-browser' or 'open-new-page', nor does it mention prerequisites like needing an active browser session. The description offers no context for usage decisions.

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