Skip to main content
Glama
Sign In

ListPlus

by ai.listplus
OverviewDiscussionsAdmin

Copy records

copy_records
Destructive

FREE (key) — copy records from one list shared with you into another (same kind: contacts or companies) — with move: true they are then hidden in the source (restorable, never deleted). A record the target already has is filled in, not doubled; a copy never goes back into a list it came through. Up to 1,000 per call.

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": {
      "from_list_id": "<from_list_id>",
      "to_list_id": "<to_list_id>"
    },
    "name": "copy_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNotrue = hide the records in the source after the copy
filterNoColumn → value: exact, { "contains": "…" }, { "not": "…" }, { "is_empty": true } or { "condition": "<one of filter_conditions>" }; ar_status by status name
languageNoLanguage of `tell_your_user` (default en)
record_idsNoThe records' ids (`id` in query_records)
to_list_idYesThe list to copy into
from_list_idYesThe list to copy from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: destructiveHint=true is reframed by explaining that move:true only hides source records ('restorable, never deleted'), and the description discloses dedupe/merge semantics ('filled in, not doubled') and an anti-cycle rule ('never goes back into a list it came through'). These are exactly the safety-critical behaviors an agent needs before invoking a flagged write operation.

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?

Compact and front-loaded — the free/key note and the copy-vs-move distinction come first, followed by dedupe and limit details. The em-dash chaining makes it slightly telegraphic to parse, but no clause is filler.

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?

Covers the semantics of a 6-parameter, nested-filter, potentially large (1,000-record) bulk mutation. The one gap is what the call returns — with no output schema and job-style siblings present, an agent can't tell whether this is synchronous or yields a job id to poll.

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, but the description adds meaning the schema lacks: it qualifies move:true as restorable-hide rather than deletion, and it restates the 1,000-record ceiling on record_ids. The nested filter object is left entirely to the schema, which is acceptable given full coverage.

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 and resource ('copy records from one list ... into another') plus a hard scope constraint ('same kind: contacts or companies'), which immediately separates it from generic writers like add_records. It never names a sibling tool to route away from, so it falls short of 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 the operative usage conditions: source list must be shared with you, both lists must be the same kind, and the per-call cap is 1,000. It also implicitly frames move:true as the 'move instead of copy' variant. No explicit 'use X instead when…' guidance against siblings such as add_records is offered.

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