Skip to main content
Glama
Sign In

ListPlus

by ai.listplus
OverviewDiscussionsAdmin

Mark records

mark_records
Destructive

FREE (key) — set a status (one of the list's, "" clears it — may start the list's rules, as in the app), add or remove tags, or hide records (restorable; hide: false shows them again) in a list shared with you for editing. Nothing is deleted.

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

Input Schema

NameRequiredDescriptionDefault
hideNotrue = hide in the list (restorable), false = show again
filterNoColumn → value: exact, { "contains": "…" }, { "not": "…" }, { "is_empty": true } or { "condition": "<one of filter_conditions>" }; ar_status by status name
statusNoA status name of the list (describe_list), or "" to clear
list_idYesThe list's id (describe_list without list_id shows the lists shared with you)
add_tagsNoTags to add
languageNoLanguage of `tell_your_user` (default en)
record_idsNoThe records' ids (`id` in query_records)
remove_tagsNoTags to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Genuinely useful beyond annotations: it warns that a status change 'may start the list's rules' (an automation side effect), reassures that hide is restorable, and states nothing is deleted. Against destructiveHint=true this is honest rather than contradictory, since hiding and tag changes are still mutations. Missing: it never says the tool only works on lists shared for editing as a failure mode, nor what the response looks like.

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 dense sentence that front-loads the pricing/auth note and covers all three operations without filler. The nested parentheses and em-dash clauses make it harder to parse than necessary, and 'FREE (key)' is cryptic in isolation.

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?

With 8 parameters, a nested filter object, no output schema, and only list_id required, the description leaves key semantics unstated: whether record_ids can be omitted in favor of filter, how filter interacts with the marking operations, and what happens when status/tags/hide are combined. It covers the operations well but not the selection model.

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 is 3. The description does add one piece of meaning the schema lacks — that status changes may trigger the list's rules — and frames list_id as an editable-shared-list constraint, but most of its parameter detail ("" clears the status, hide: false restores) simply restates the schema descriptions.

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 set of operations (set status, add/remove tags, hide) on a clear resource (records in a shared list) and adds a distinguishing scope note ('Nothing is deleted'). It does not name update_records or any sibling as the alternative for broader field edits, so the boundary is only implied.

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?

Provides one real gating condition — the list must be 'shared with you for editing' — plus the 'FREE (key)' pricing/auth hint. It never says when to prefer this over update_records, when to use tags versus status versus hide, or what happens when several operations are combined in one call.

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