Skip to main content
Glama
davidashman

AnyList MCP Server

by davidashman

Get Lists

get_lists

Retrieve all shopping lists from your AnyList account to view, manage, or organize items for shopping and meal planning.

Instructions

List all shopping lists in the AnyList account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the "get_lists" tool, which fetches lists from the AnyListClient and formats them for the MCP response.
    async () => {
      try {
        const client = AnyListClient.getInstance();
        const lists = await client.getLists();
    
        const result = lists.map((l) => ({
          id: l.identifier,
          name: l.name,
          itemCount: l.items.length,
          uncheckedCount: l.items.filter((i) => !i.checked).length,
        }));
    
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error fetching lists: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true,
        };
      }
    },
  • The registration of the "get_lists" tool within the McpServer.
    server.registerTool(
      'get_lists',
      {
        title: 'Get Lists',
        description: 'List all shopping lists in the AnyList account.',
        inputSchema: z.object({}),
      },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. While 'List' implies a read-only operation, the description lacks crucial behavioral details: authentication requirements, rate limits, pagination behavior, or the structure/format of the returned list data.

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?

Single sentence of eight words with zero redundancy. Information is front-loaded and every word serves a purpose in defining scope and resource.

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

Completeness3/5

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

Adequate for a simple parameterless tool, but gaps remain: without an output schema, the description should ideally specify what list attributes are returned (IDs, names, metadata). However, given the low complexity, it meets minimum viability.

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

Parameters4/5

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

The input schema has zero parameters, which establishes a baseline score of 4 per evaluation guidelines. The description appropriately signals no filtering capabilities by stating 'all' lists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description uses specific verb 'List' with clear resource 'shopping lists' and scope 'in the AnyList account'. It effectively distinguishes from sibling 'get_list_items' by specifying 'all shopping lists' (plural, account-level) versus items within a specific list.

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 name and description (use when you need to retrieve all lists), but there are no explicit when-to-use guidelines, prerequisites, or contrasts with alternatives like 'get_list_items'.

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/davidashman/anylist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server