ListPlus

Create a rule

create_trigger

FREE (key, Set up) to set up — a rule (trigger) of a list: when a record is new / changed / meets the conditions, set a status (a new name is created), add a tag, hide it (it leaves the normal flow: no checks, rules, enrichment or sync — restorable), hand it to an EXISTING pipeline (pipelines are made by a person in the app), or ENRICH it — PAID per hit, at most budget_per_record credits per record, on THIS connection's day budget (an empty day makes the rule wait, never overspend). Active at once unless activate: false — set an enrich rule up paused until your user agreed to the budget. include_existing runs it once for the records already in the list. Status, tag and hide need Edit on the list; a pipeline the pipeline's share; enrich Full. Call describe_setup first for the fields and operators.

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": "<name>",
      "on": "<on>",
      "actions": "<actions>"
    },
    "name": "create_trigger"
  }
}

Input Schema

Name	Required	Description
`on`	Yes	new: new records · changed: changed ones · match: new or changed, once they meet the conditions
`name`	Yes
`actions`	Yes
`list_id`	Yes	The list's id (describe_list shows the lists shared with you)
`activate`	No	Default true
`language`	No	Language of `tell_your_user` and of Yes/No words in new columns (default en)
`conditions`	No	Groups are OR-ed, the conditions inside a group AND-ed: { groups: [[cond, cond], [cond]] }
`include_existing`	No	Also run once for the records already in the list

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses important behavior: enrich is paid per hit and capped by budget and the connection's day budget, empty day budgets make the rule wait, hide removes records from normal flow but is restorable, and rules are active immediately unless paused. These are material mutation and cost details not covered by the annotations.

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 dense and packed into one long paragraph with awkward phrasing such as 'FREE (key, Set up) to set up', which hurts readability. Most content is useful given the tool's complexity, but it is not cleanly front-loaded and would benefit from structure.

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 complex creation tool with nested action objects, conditional logic, paid enrichment, and permissions, the description covers the critical behavioral and setup context. The main gap is that it does not describe the return value or created trigger identifier, and no output schema exists to fill that 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?

The description adds substantial meaning beyond the schema for complex parameters such as the action kinds, budget_per_record, activate, and include_existing. It does not explain every parameter, notably name, language, or the detailed conditions grouping, but it compensates by pointing to describe_setup and the schema already covers those areas reasonably well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: setting up a rule/trigger on a list, with trigger conditions and actions spelled out. It also distinguishes the action types (status, tag, hide, pipeline, enrich), so an agent can tell what this tool does without inspecting siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explains when the rule fires, how each action behaves, when to use activate: false for enrich rules, what include_existing does, and what permissions are needed. It also directs the agent to call describe_setup first for fields and operators, giving clear setup guidance.

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?