Skip to main content
Glama
yfmeii

WeChat Mini Program Dev MCP

by yfmeii

mp_navigate

Navigate between pages in WeChat Mini Programs using methods like navigateTo, redirectTo, reLaunch, switchTab, and navigateBack to control page flow during development.

Instructions

在小程序内导航,支持 navigateTo、redirectTo、reLaunch、switchTab 和 navigateBack。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNo
pathNo
queryNo
transitionNonavigateTo
waitMsNo

Implementation Reference

  • The async execute function implementing the core logic of mp_navigate: parses args, performs navigation (navigateTo, redirectTo, etc., or back) using miniProgram methods, optionally waits, and returns active page info.
    execute: async (rawArgs, context: ToolContext) => {
      const args = navigateParameters.parse(rawArgs ?? {});
      const transition = args.transition ?? "navigateTo";
      const overrides = args.connection;
      const waitMs = args.waitMs;
      const providedPath = args.path;
    
      return manager.withMiniProgram<ContentResult>(
        context.log,
        { overrides },
        async (miniProgram) => {
          let url: string | undefined;
          let page;
    
          if (transition === "navigateBack") {
            page = await miniProgram.navigateBack();
          } else {
            if (!providedPath) {
              throw new UserError(
                "参数 path 是必需的,除非 transition 是 navigateBack。"
              );
            }
            url = buildUrl(providedPath, args.query);
            switch (transition) {
              case "navigateTo":
                page = await miniProgram.navigateTo(url);
                break;
              case "redirectTo":
                page = await miniProgram.redirectTo(url);
                break;
              case "reLaunch":
                page = await miniProgram.reLaunch(url);
                break;
              case "switchTab":
                page = await miniProgram.switchTab(url);
                break;
              default:
                throw new UserError(`不支持的 transition: ${transition}`);
            }
          }
    
          if (waitMs && page) {
            await page.waitFor(waitMs);
          }
    
          const activePage = page ?? (await miniProgram.currentPage());
    
          return toTextResult(
            formatJson({
              transition,
              url,
              activePage: activePage
                ? { path: activePage.path, query: activePage.query }
                : null,
            })
          );
        }
      );
  • Zod schema for mp_navigate input parameters: connection, path (optional), query, transition (default navigateTo), waitMs (optional).
    const navigateParameters = connectionContainerSchema
      .extend({
        path: z.string().trim().min(1).optional(),
        query: querySchema,
        transition: z
          .enum([
            "navigateTo",
            "redirectTo",
            "reLaunch",
            "switchTab",
            "navigateBack",
          ])
          .default("navigateTo"),
        waitMs: z.coerce.number().int().nonnegative().optional(),
      });
  • Factory function creating array of application tools, including createNavigateTool(manager) which defines mp_navigate.
    export function createApplicationTools(
      manager: WeappAutomatorManager
    ): AnyTool[] {
      return [
        createEnsureConnectionTool(manager),
        createNavigateTool(manager),
        createScreenshotTool(manager),
        createCallWxMethodTool(manager),
        createGetConsoleLogsTool(manager),
      ];
    }
  • src/tools.ts:7-13 (registration)
    Main tools factory that includes application tools (with mp_navigate) along with page and element tools.
    export function createTools(manager: WeappAutomatorManager): AnyTool[] {
      return [
        ...createApplicationTools(manager),
        ...createPageTools(manager),
        ...createElementTools(manager),
      ];
    }
  • src/index.ts:17-17 (registration)
    Adds all tools (including mp_navigate) to the FastMCP server instance.
    server.addTools(createTools(manager));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it lists the navigation methods, it doesn't explain what each method does behaviorally (e.g., navigateTo adds to navigation stack, redirectTo replaces current page, reLaunch closes all pages). It also doesn't mention error conditions, permission requirements, or what happens after navigation completes. The description provides minimal behavioral context beyond naming the available transitions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise - a single sentence that states the core purpose and lists the supported methods. There's no wasted verbiage or redundant information. However, it could be slightly more front-loaded by emphasizing the primary action before listing the specific methods.

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?

For a navigation tool with 5 parameters (including a complex nested object), 0% schema description coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain parameter usage, behavioral outcomes, error handling, or integration with sibling tools like mp_ensureConnection. The tool appears to be a core navigation function within a mini-program testing framework, but the description provides minimal context for proper usage.

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

Parameters2/5

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

With 0% schema description coverage and 5 parameters (including a complex nested 'connection' object with 12 sub-properties), the description provides no parameter information whatsoever. It doesn't explain what 'path', 'query', 'transition', 'waitMs', or the 'connection' object are for, nor how they interact. The description fails to compensate for the complete lack of schema documentation.

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's purpose: '在小程序内导航' (navigate within mini-programs) and lists the specific navigation methods supported (navigateTo, redirectTo, reLaunch, switchTab, navigateBack). It provides a specific verb ('导航' - navigate) and resource ('小程序' - mini-programs), but doesn't explicitly differentiate from sibling tools like page_waitElement or mp_ensureConnection, which have different purposes.

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 (like needing an established connection via mp_ensureConnection), nor does it explain when to choose different transition types (navigateTo vs redirectTo vs reLaunch). There's no comparison with sibling tools that might handle similar navigation scenarios differently.

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/yfmeii/weapp-dev-mcp'

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