AnyList MCP Server

anylist_click

Clicks a numbered element on the current AnyList page, letting an AI agent open, select, or act on items, lists, and recipes identified from the last read.

Instructions

Click a numbered element on the current AnyList page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "anylist_click"
  }
}

Input Schema

Name	Required	Description	Default
`element`	Yes	Element number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses very little. It does not say what the click does (navigate, submit, toggle), whether element numbering is invalidated after the click, what happens if the number is out of range, or whether any confirmation is returned; "current page" is the only hint of state dependency.

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?

One front-loaded sentence with no filler or repetition. It is efficient, though its terseness leaves the state and sequencing context unstated rather than placed elsewhere.

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 stateful browser-automation click with no annotations and no output schema, the definition omits the essential facts an agent needs: how the element index is obtained, whether a prior read is required, and what changes after the click. The one-line description is thin relative to that complexity.

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?

Schema description coverage is 100% and the single parameter is already documented as "Element number from the last read," so the baseline is 3. The word "numbered" in the description reinforces that link, but it adds no format or validity detail beyond what the schema states.

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?

States a specific verb and object: "Click a numbered element on the current AnyList page." That is enough to distinguish it from anylist_type (text entry) and anylist_read (page reading) without opening another schema. It stops short of naming those siblings explicitly, which keeps it at 4 rather than 5.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. It does not say that it should follow an anylist_read or anylist_open, nor when to prefer it over anylist_type, so the agent must infer the sequencing from the sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server