Skip to main content
Glama
Sign In

ListPlus

by ai.listplus
OverviewDiscussionsAdmin

Update records

update_records

FREE (key) — change cells of a list shared with you for editing: per record (records: [{ id, column: value }]) or one change for many (record_ids or filter + set). Only the columns you may write (describe_list); only_empty fills empty cells only.

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

Input Schema

NameRequiredDescriptionDefault
setNoWith record_ids or filter: column → new value
filterNoColumn → value: exact, { "contains": "…" }, { "not": "…" }, { "is_empty": true } or { "condition": "<one of filter_conditions>" }; ar_status by status name
list_idYesThe list's id (describe_list without list_id shows the lists shared with you)
recordsNoPer record: { id, <column>: <value>, … }
languageNoLanguage of `tell_your_user` (default en)
only_emptyNoFill empty cells only
record_idsNoThe records' ids (`id` in query_records)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description adds useful behavior: it is free/key-based, requires edit access to the list, is constrained to writable columns, and `only_empty` limits changes to empty cells. It does not fully describe overwrite semantics or failure behavior, but it is consistent with `readOnlyHint: false` and `destructiveHint: false`.

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?

The description is a single dense but front-loaded sentence that puts the main action and cost note first, then explains modes and constraints. It is efficient, though the parenthetical notation makes it slightly harder to scan than it could be.

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?

For a seven-parameter mutation tool with nested objects and no output schema, the description covers the key invocation modes, permissions, and the `only_empty` constraint. It does not describe return values or partial-failure behavior, but the schema and annotations carry enough of the remaining structure that it is close to complete.

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 per-parameter descriptions already carry much of the meaning. The tool description adds cross-parameter guidance by explaining that `records` updates one row at a time while `record_ids` or `filter` combine with `set` for bulk changes, and it ties `only_empty` to its fill-only behavior.

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 states a specific action ("change cells") and resource ("a list shared with you for editing"), and clarifies that it updates existing records rather than adding new ones. It does not explicitly name adding-related siblings such as add_records, so it stops short of full sibling differentiation.

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?

It clearly explains the two update modes: per-record `records` and bulk `record_ids` or `filter` with `set`. It also states the prerequisite that the list must be shared for editing and that only writable columns may be changed, but it does not explicitly exclude sibling alternatives.

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

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