ListPlus

Create a list

create_list

FREE (key, Set up) — a new list in the workspace (contacts or companies), with the standard columns or the content types you name, and optional statuses. It is this agent's own list: shared in Full. Then add_column, create_trigger, add_records.

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

Input Schema

Name	Required	Description
`kind`	No	Default contacts
`name`	Yes
`columns`	No	Content types (first_name, email, company_name, company_domain, job_title, linkedin_profile_url …); absent = the standard columns
`language`	No	Language of `tell_your_user` and of Yes/No words in new columns (default en)
`statuses`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, open-world operation. The description adds useful behavioral context by saying the list belongs to this agent and is shared in Full, plus a cryptic 'FREE' signal, but it does not explain duplicate-name handling, permissions, or what is returned after creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but front-loads a cryptic 'FREE (key, Set up)' fragment before stating the action. The follow-on tool list is useful, but the abbreviations and dense parentheticals reduce immediate clarity.

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?

For a six-parameter creation tool with no output schema and only half of its parameters documented in the schema, the description is adequate but incomplete. It covers purpose, some parameters, ownership/sharing, and follow-on tools, but omits return values and several parameter semantics an agent may need before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, so the description must compensate. It clarifies the kind options, the default-versus-explicit columns behavior, and optional statuses, but it leaves language, description, and the required name parameter semantically thin.

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 verb and resource: creating a new list in the workspace for contacts or companies, with standard or named columns and optional statuses. It clearly identifies this as a creation tool, though it does not explicitly distinguish it from list-inspection siblings such as check_list or describe_list.

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 description implies a setup workflow through the parenthetical 'Set up' and the follow-on sequence 'Then add_column, create_trigger, add_records.' However, it gives no explicit when-not guidance or alternatives for creating versus checking, describing, or fixing an existing 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?