Skip to main content
Glama
yfmeii

WeChat Mini Program Dev MCP

by yfmeii

page_setData

Update data on the current page in WeChat Mini Program development to modify UI state and trigger re-rendering.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNo
dataYes

Implementation Reference

  • The main handler implementation for the 'page_setData' tool. It parses the input arguments, extracts data keys, and uses the page.setData method to update the page data, returning a confirmation message.
    function createSetPageDataTool(manager: WeappAutomatorManager): AnyTool {
      return {
        name: "page_setData",
        description: "使用 setData 更新当前页面的数据。",
        parameters: setPageDataParameters,
        execute: async (rawArgs, context: ToolContext) => {
          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(", ") : "(无)"}。`
              );
            }
          );
        },
      };
    }
  • Zod schema defining the input parameters for the page_setData tool, including the 'data' record and inherited connection properties.
    const setPageDataParameters = connectionContainerSchema.extend({
      data: z.record(z.unknown()),
    });
  • Page tools factory function that registers the page_setData tool among other page tools.
    export function createPageTools(manager: WeappAutomatorManager): AnyTool[] {
      return [
        createGetElementTool(manager),
        createWaitForElementTool(manager),
        createWaitForTimeoutTool(manager),
        createGetPageDataTool(manager),
        createSetPageDataTool(manager),
        createCallPageMethodTool(manager),
      ];
    }
  • src/tools.ts:7-13 (registration)
    Main tools factory that includes page tools (containing page_setData) by spreading createPageTools.
    export function createTools(manager: WeappAutomatorManager): AnyTool[] {
      return [
        ...createApplicationTools(manager),
        ...createPageTools(manager),
        ...createElementTools(manager),
      ];
    }
  • src/index.ts:17-17 (registration)
    Final registration of all tools (including page_setData) to the FastMCP server.
    server.addTools(createTools(manager));
Behavior1/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 but provides almost none. 'Updates current page data' implies a mutation operation, but there's no information about permissions needed, side effects, error conditions, rate limits, or what constitutes success/failure. The description doesn't mention that this requires a connection parameter or what happens if the update fails.

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 - a single sentence in Chinese that translates to 'Use setData to update current page data.' While this is too brief for adequate documentation, it's efficiently structured with zero wasted words. Every word contributes to the core message, making it maximally concise.

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?

Given the complexity (2 parameters including a highly complex nested object), complete lack of annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what the tool returns, what errors might occur, what the connection parameter does, or how the data parameter should be structured. For a mutation tool with such complex parameters, this minimal description is insufficient.

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?

With 0% schema description coverage and 2 parameters (one complex nested object with 13 properties), the description provides no parameter information whatsoever. It doesn't mention the 'data' parameter that's required, nor the optional 'connection' parameter with its numerous sub-properties. 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.

Purpose3/5

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

The description states the tool 'updates current page data' which provides a basic verb+resource combination. However, it's vague about what 'data' refers to and doesn't distinguish this from sibling tools like 'element_setData' or 'page_getData'. The purpose is understandable but lacks specificity about what kind of page data is being updated.

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. There are multiple sibling tools that interact with page data (page_getData, element_setData, page_callMethod), but the description doesn't indicate when this specific tool is appropriate versus those alternatives. No context about prerequisites or typical use cases is provided.

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