Skip to main content
Glama
Sign In
AnyList MCP Server

AnyList MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

anylist_open

Open an AnyList page in your signed-in Cloud Browser to manage shopping lists, recipes, and meal plans.

Instructions

Open a AnyList page in your signed-in Cloud Browser (default https://www.anylist.com) to work with shopping lists, recipes and meal plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "anylist_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.anylist.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the page opens in the signed-in Cloud Browser and that the target defaults to https://www.anylist.com, but says nothing about what happens on navigation failure, whether prior browser state is replaced, or what is returned after opening.

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?

A single front-loaded sentence with no wasted clauses; the only blemish is the grammatical slip 'a AnyList' and the parenthetical default duplicating the schema.

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

Completeness4/5

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

The tool is simple—one optional parameter, no output schema, no nested objects—and the description covers what it does and the sign-in precondition. The main gap is the follow-on workflow (that further reading requires anylist_read), which is a minor omission at this complexity level.

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?

There is only one optional parameter and the schema already documents it fully (including the default), so the description only restates the default URL. Baseline 3 applies when schema coverage is complete.

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 gives a specific verb+resource: 'Open a AnyList page in your signed-in Cloud Browser', plus the domain of use (shopping lists, recipes, meal plans). It is clearly distinguishable from siblings like anylist_click, anylist_read and anylist_close, though it never calls out that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the stated purpose and the 'signed-in Cloud Browser' precondition, but there is no explicit guidance on when to open a page versus reading it with anylist_read or using anylist_guide, and no when-not guidance.

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

Deploy Server

Other Tools