Skip to main content
Glama
Sign In

ListPlus

by ai.listplus
OverviewDiscussionsAdmin

Add records

add_records

FREE (key) — add records (JSON objects, column names or common field names) to a list shared with you for editing. A record the list already has (same e-mail, LinkedIn, name + company) is filled in, not doubled. Up to 1,000 per call; the answer names each new record's id and url and what was rejected.

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>",
      "records": "<records>"
    },
    "name": "add_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesThe list's id (describe_list without list_id shows the lists shared with you)
recordsYesThe records as JSON objects
languageNoLanguage of `tell_your_user` (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, open-world write; the description goes much further by disclosing the dedupe keys (e-mail, LinkedIn, name + company), the 1,000-record cap, and that the response names each new record's id and url plus what was rejected. That is substantive behavioral context beyond the structured fields.

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?

Three tight sentences, front-loaded with cost and action, then dedupe semantics, then limits and return shape — every clause carries information an agent needs. The telegraphic style ('FREE (key) —') is compact rather than vague.

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 write tool with no output schema, the description covers return values, batch limits, and duplicate handling, which is most of what an agent needs. It does not say whether a rejected record aborts the batch or how partial failures affect the 1,000-record cap, a minor but real gap.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning about `records` — that objects may use column names or common field names, and that matching is by e-mail, LinkedIn, or name + company. `list_id` and `language` get nothing beyond the schema, which already documents them well.

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 ('add records ... to a list shared with you for editing') plus the upsert nuance ('filled in, not doubled'), which separates it from a pure update or check tool. It does not explicitly name a sibling such as update_records as the alternative, so it falls 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 Guidelines3/5

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

The prerequisite is clear — the list must be shared with you for editing — and 'FREE (key)' flags cost. But there is no explicit when-not guidance or pointer to check_records / update_records for the cases this tool does not cover, leaving usage context implied.

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