ListPlus

Query records

query_records

Read-only

FREE (key) — read records of a list shared with you: mode rows (default; columns you may see, each with id and url), count, or ids (up to 10,000, to pass on as record_ids). Filter by column values or conditions (describe_list names them).

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": {
      "list_id": "<list_id>"
    },
    "name": "query_records"
  }
}

Input Schema

Name	Required	Description
`mode`	No	rows (default), count, or ids
`limit`	No	Rows per call (capped by the list's share, default 100)
`logic`	No	How several filter entries combine (default and)
`filter`	No	Column → value: exact, { "contains": "…" }, { "not": "…" }, { "is_empty": true } or { "condition": "<one of filter_conditions>" }; ar_status by status name
`offset`	No	Skip this many rows (paging)
`columns`	No	Only these columns in the rows
`list_id`	Yes	The list's id (describe_list without list_id shows the lists shared with you)
`language`	No	Language of `tell_your_user` (default en)
`include_hidden`	No	Also records hidden in the list (status "ignored")

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only/non-destructive semantics, and the description adds genuinely new facts: the operation is free (key-based), ids mode caps at 10,000, and limit is bounded by the list's share. It doesn't discuss error behavior or throttling, but it exceeds the annotation baseline.

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 sentence with no filler, and the free/read framing is front-loaded before the mode details. The dense parentheticals and backticks make it slightly harder to scan than an ideal definition.

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?

With 9 parameters, a nested filter object, and no output schema, the description does enough: it explains what each mode returns and where filter condition names come from. Paging via offset/limit and language handling are left entirely to the schema, which is acceptable but not fully covered.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema lacks: rows carry per-column id and url, ids output is intended as record_ids input, and filter entries can reference filter_conditions from describe_list. These workflow semantics go beyond the enum labels in the schema.

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+resource ('read records of a list shared with you') and enumerates the three output modes (rows, count, ids), so the agent knows exactly what it retrieves. It does not explicitly differentiate itself from close siblings like check_records, which keeps it from a 5.

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

Usage Guidelines4/5

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

Gives usable context: filter via column values or conditions whose names come from describe_list, and use ids mode when results are to be passed on as record_ids. Missing an explicit 'use X instead when…' statement against siblings such as check_records or describe_list.

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

All ListPlus 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?