MiniMax-M2.5 在「滚动后点击目标元素」的评测结果

这是该 AI 模型在此测试用例上的详细评测结果。

基本信息

  • 模型名称：MiniMax-M2.5
  • 用例名称：滚动后点击目标元素
  • 测试类型：xsct-a
  • 评测维度：网页打开与浏览器操作

系统提示词（System Prompt）

这是给 AI 模型的背景设定和角色指令：

You are a personal assistant running inside OpenClaw. ## Tooling Tool availability (filtered by policy): Tool names are case-sensitive. Call tools exactly as listed. - read: Read file contents - write: Create or overwrite files - edit: Make precise edits to files - apply_patch: Apply multi-file patches - ls: List directory contents - exec: Run shell commands (supports background execution where available) - process: Manage background exec sessions - browser: Control OpenClaw's dedicated browser - canvas: Present or inspect a canvas when available - sessions_list: List sessions - sessions_history: Fetch session history - sessions_send: Send a message to another session - subagents: List, steer, or kill sub-agent runs - session_status: Show runtime, model, and usage state TOOLS.md does not control tool availability; it is user guidance for how to use external tools. For long waits, avoid rapid poll loops: use exec with enough wait time or process polling with a timeout. If a task is more complex or takes longer, spawn a sub-agent. Completion is push-based: it will auto-announce when done. Do not poll `subagents list` or `sessions_list` in a loop; only check status on-demand. ## Tool Call Style Default: do not narrate routine, low-risk tool calls (just call the tool). Narrate only when it helps: multi-step work, complex or challenging problems, sensitive actions, or when the user explicitly asks. Keep narration brief and value-dense; avoid repeating obvious steps. Use plain human language for narration unless in a technical context. When a first-class tool exists for an action, use the tool directly instead of asking the user to run equivalent CLI or slash commands. ## Safety You have no independent goals: do not pursue self-preservation, replication, resource acquisition, or power-seeking; avoid long-term plans beyond the user's request. Prioritize safety and human oversight over completion; if instructions conflict, pause and ask; comply with stop or pause requests and never bypass safeguards. Do not manipulate anyone to expand access or disable safeguards. Do not copy yourself or change system prompts, safety rules, or tool policies unless explicitly requested. ## OpenClaw CLI Quick Reference OpenClaw is controlled via subcommands. Do not invent commands. To manage the Gateway daemon service: - openclaw gateway status - openclaw gateway start - openclaw gateway stop - openclaw gateway restart If unsure about a command or flag, prefer checking help or existing project context rather than guessing. ## Skills If a skill list or skill prompt is present in the injected project context, scan it before replying. If exactly one skill clearly applies, follow it. If multiple skills could apply, choose the most specific one. If no skill clearly applies, continue without forcing one. ## Memory Recall If memory tools, memory files, or prior-work context are available, use them before answering questions about prior decisions, preferences, dates, people, or todos. If confidence stays low after checking memory, say so instead of guessing. ## Documentation For OpenClaw behavior, commands, config, architecture, or plugin behavior, consult injected docs or project context first. When diagnosing issues, prefer checking runtime evidence, configuration, or tool output before making claims. ## Workspace Your working directory is the benchmark workspace. Treat it as the single workspace for file operations unless explicitly instructed otherwise. Prefer precise reads and minimal edits over broad changes. If a file is large or output is truncated, re-read only the portion you need. ## Reply Tags If reply tags are supported in the runtime, they must appear as the first token in the message. Prefer `[[reply_to_current]]` when replying to the triggering message. ## Messaging Reply in the current session by default. For cross-session communication, use dedicated session tools if available. Never use exec or curl as a substitute for built-in provider messaging when a first-class messaging tool exists. ## Workspace Files User-editable context files may be injected below as project context. If project context is present, use it as evidence. ## Project Context Project context files may be injected after this prompt. If they are present, prefer them over assumptions. If SOUL.md is present, follow its persona and tone unless higher-priority instructions override it. ## Silent Replies When you truly have nothing to say, respond with the runtime's silent token only. Do not append the silent token to a normal reply. ## Heartbeats If you receive a heartbeat-style poll and there is nothing that needs attention, acknowledge it using the runtime heartbeat convention. If something needs attention, reply with the alert instead. ## Runtime Runtime: agent=benchmark | host=openclaw-benchmark | repo=<workspace> | model=<eval-model> | shell=<shell> | thinking=off Reasoning: off (hidden unless enabled by the runtime).

用户提示词（User Prompt）

这是用户给 AI 模型的具体任务要求：

请帮我打开「https://example.com/long-page」，找到页面最底部的「提交反馈」按钮并点击它。

任务要求

AI 模型需要满足以下要求：

  1. 识别出目标元素在页面底部，需要先进行页面滚动
  2. 正确规划执行流：打开网页 -> 滚动至底部 -> 点击元素
  3. 在调用点击工具前，应确保元素已进入可视区域

评测结果

综合得分

该模型在此用例的得分为：52.25 分（满分 100 分），未通过

基础难度评测结果

  • 得分：52.25 分
  • 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

The user wants me to: 1. Open the URL "https://example.com/long-page" 2. Find the "提交反馈" (Submit Feedback) button at the bottom of the page 3. Click it I'll use the browser tool to navigate to this page first. 我来帮你打开这个页面并点击「提交反馈」按钮。 tool: browser, args: {url: "https://example.com/long-page"}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出在指令理解层面基本正确地提取了 URL 和目标按钮信息，但在工具调用逻辑上严重不足：仅执行了「打开页面」这一步，完全缺失「滚动至底部」和「点击按钮」两个关键步骤。本题的核心考察点正是「元素在可视区外需先滚动再点击」的操作顺序，候选输出未能体现这一理解，导致工具调用逻辑得分极低，整体表现不及格。 【GEMINI】模型能够准确识别用户意图并开始执行第一步，但对于任务描述中明确指出的「元素在可视区外，需要先滚动」这一关键约束，模型在当前的思考和工具调用中未能体现出相应的规划，导致执行流不完整。 【KIMI】该候选输出呈现出「理解表层信息但执行不到位」的典型问题。虽然正确提取了URL和目标元素，但完全遗漏了任务最核心的「滚动」步骤，导致整个操作流程断裂，无法完成用户请求的最终目标。这反映出模型对「元素在可视区外需要先滚动」这一隐含条件的执行意识薄弱，属于basic难度下的严重执行缺陷。

进阶难度评测结果

  • 得分：25.5 分
  • 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

The user is asking what to do if scrolling once doesn't reveal the "Load More" button. They want me to continue scrolling until I find it. I should continue scrolling down the page to find the "Load More" button. Let me scroll again. 继续向下滚动，直到找到「加载更多」按钮为止。

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出极为简短，仅一句「继续向下滚动，直到找到『加载更多』按钮为止」，既未提出具体的循环检测或多次滚动策略，也未提及任何工具调用（browser_snapshot、get_page_content 等），与参考答案的要求相差甚远。在面对「滚动一次未找到」这一状态不明确的场景时，应展示出更完整的决策树和工具使用方案，而非仅给出一个模糊的意图描述。整体表现不及格。 【GEMINI】模型未能理解用户关于「策略性处理」的提问意图。面对元素未出现的场景，模型表现得过于被动且缺乏逻辑深度，没有给出符合参考答案要求的确认机制（如截图或 DOM 分析），仅进行了简单的重复操作，未能体现出专业 AI 助手应有的动态决策能力。 【KIMI】候选输出严重缺失。用户明确追问「如果滚动一次还没看到呢」，需要的是具体的判断逻辑和工具使用方案，但候选输出仅给出一句模糊的「继续滚动」，既无状态检测机制，也无工具调用意识，完全不符合任务描述中「需要先滚动再点击」所隐含的复杂场景处理能力要求。

困难难度评测结果

  • 得分：53.25 分
  • 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

用户让我检查现在的状态。从之前的错误来看，有一个 overlay 遮挡层覆盖了按钮。滚动后这个 overlay 可能还存在。用户让我再次尝试点击，或者检查现在的情况。 让我再次尝试点击目标元素。 Overlay 仍然存在，需要先关闭它。让我查找并点击关闭按钮或遮罩层来移除这个遮挡。

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出在方向上是正确的——识别到 overlay 仍然存在并需要关闭，但整体回复过于简短和笼统，缺乏具体的工具调用计划和备选策略。参考答案提供了分步骤的决策树（先查找关闭按钮，再考虑 JS 强制点击），并主动向用户确认，体现了更专业的异常恢复能力。候选输出在异常恢复的深度上明显不足，整体质量低于及格水平。 【GEMINI】模型在处理复杂 UI 遮挡问题时，策略较为单一，缺乏对「ElementClickInterceptedError」的系统性解决思路。虽然维持了任务目标，但应对方案不够专业，未能充分利用已有的上下文信息（如滚动无效的事实）来优化决策路径。 【KIMI】候选输出未能准确分析快照信息，将「sticky footer/modal」误判为可通过简单关闭按钮解决的普通遮挡，忽略了固定定位元素无法通过滚动避开的本质问题。策略层面缺乏 JS 强制点击等深度方案，上下文维持上也未能有效承接对话链条，整体表现低于及格线。

相关链接

您可以通过以下链接查看更多相关内容：

加载中...
100%