Skip to main content
Glama
yfmeii

WeChat Mini Program Dev MCP

by yfmeii

page_setData

Update the current page's data using the setData method for WeChat mini program development automation.

Instructions

使用 setData 更新当前页面的数据。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNo
dataYes

Implementation Reference

  • The handler function 'createSetPageDataTool' that implements the 'page_setData' tool logic. It accepts 'data' parameter (a record of string keys to unknown values) and calls 'page.setData(args.data)' via the manager.
    function createSetPageDataTool(manager: WeappAutomatorManager): AnyTool {
      return {
        name: "page_setData",
        description: "使用 setData 更新当前页面的数据。",
        parameters: setPageDataParameters,
        execute: async (rawArgs, context: ToolContext) =>
          withUserErrorResult(async () => {
          const args = setPageDataParameters.parse(rawArgs ?? {});
          const dataKeys = Object.keys(args.data ?? {});
          return manager.withPage<ContentResult>(
            context.log,
            { overrides: args.connection },
            async (page) => {
              await page.setData(args.data);
              return toTextResult(
                `已更新页面数据键: ${dataKeys.length ? dataKeys.join(", ") : "(无)"}。`
              );
            }
          );
          }),
      };
    }
  • The 'setPageDataParameters' Zod schema for the 'page_setData' tool, defining the 'data' input parameter as z.record(z.string(), z.unknown()).
    const setPageDataParameters = connectionContainerSchema.extend({
      data: z.record(z.string(), z.unknown()),
    });
  • The 'createPageTools' function registers all page tools, including 'createSetPageDataTool' at line 59. This is part of the registration chain that collects all tools.
    export function createPageTools(manager: WeappAutomatorManager): AnyTool[] {
      return [
        createGetElementTool(manager),
        createGetElementsTool(manager),
        createWaitForElementTool(manager),
        createWaitForTimeoutTool(manager),
        createGetPageDataTool(manager),
        createSetPageDataTool(manager),
        createCallPageMethodTool(manager),
      ];
    }
  • src/tools.ts:7-13 (registration)
    Top-level 'createTools' function that aggregates all tool groups, including 'createPageTools' which contains 'page_setData'.
    export function createTools(manager: WeappAutomatorManager): AnyTool[] {
      return [
        ...createApplicationTools(manager),
        ...createPageTools(manager),
        ...createElementTools(manager),
      ];
    }
Behavior2/5

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

Only states that it updates data, with no details on side effects, permissions, or error conditions. No annotations provided to supplement.

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

Conciseness3/5

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

Single sentence is concise but too brief, missing essential context for effective use.

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

Completeness1/5

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

With no annotations, output schema, or parameter descriptions, the description is severely incomplete for a tool that modifies page data.

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

Parameters1/5

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

Schema has 0% description coverage and the description adds no information about parameters. The required 'data' parameter remains undocumented.

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 (update) and target (current page's data), but lacks differentiation from sibling tools like element_setData or page_getData.

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 on when to use this tool versus alternatives like element_setData or page_getData, nor any conditions or prerequisites.

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