LastList

Search lists

search_lists

Read-only

Lists the user's real LastList lists, returning each one's id, title, type and item count. This is where list ids originate: the ids accepted by the other list tools are the ones returned here. With no arguments it returns every list the user has, and the optional type filter narrows it. It returns the lists themselves rather than their contents; get_list returns the items on one.

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": "search_lists"
  }
}

Input Schema

Name	Required	Description	Default
`listType`	No	Only return lists of this type. shopping = things to buy; inventory = what the user already has at home (their pantry); wishlist = things they want eventually; packing = for a trip; task = to-dos; note = free text. Omit to return every list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / listType / description

Previous value: -"Optional filter: only return lists of this type"New value: +"Only return lists of this type. shopping = things to buy; inventory = what the user already has at home (their pantry); wishlist = things they want eventually; packing = for a trip; task = to-dos; note = free text. Omit to return every list."

First observedOct 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds useful semantics the annotation cannot: the full result set is returned by default, and this is the id authority for sibling tools. It does not discuss result ordering, pagination, or empty-list behavior, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the resource and returned fields, then scope, then the sibling distinction. Nothing is repeated and every sentence carries new information.

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

Completeness5/5

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

For a one-optional-param read tool with no output schema, the description names the returned fields, the default scope, and the id-provenance relationship to sibling tools. An agent has everything needed to call it correctly.

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 coverage is 100% and the enum values are thoroughly documented in the schema itself, so the schema does the heavy lifting. The description only restates that the type filter narrows results, adding no format or edge-case detail beyond what the parameter description already says.

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?

States a specific verb and resource (lists the user's real LastList lists) plus the exact payload returned (id, title, type, item count). It also explicitly separates itself from get_list by noting it returns lists, not their contents, so an agent can pick the right tool without opening the schema.

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

Usage Guidelines5/5

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

Gives the default invocation behavior (no arguments returns every list), the narrowing condition (optional type filter), and names the alternative for the adjacent need (get_list returns the items). It additionally explains why this tool matters: it is the origin of list ids consumed by the other list tools.

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

All LastList tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?