ListPlus

Load companies

load_companies

PAID (needs a key) — 0.25 credits per company delivered (25 companies = 6.25 credits): the companies a count_companies question found, into a company list in ListPlus — name, domain, website, industry, size, place, LinkedIn page. 10, 25, 50 per call (limit), a cursor for the next ones. The same page within an hour costs nothing again. estimate:true shows the price (free, no key).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "load_companies"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Companies in this call: 10, 25, 50 (default 25)
`cursor`	No	From the last answer: the next companies into the same list
`filters`	No	Company filters — exact values from search_options (for: companies)
`list_id`	No	Append to this list of the workspace (default: a new list per search)
`estimate`	No	true = the filters as understood and the price, nothing runs (free, no key)
`language`	No	Language of `tell_your_user` (default en)
`list_name`	No	The new list's name
`max_credits`	No	The most this call may cost; it loads fewer pages / refuses rather than spend more

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations, which only say it is not read-only and non-destructive: it discloses that a key is required, the exact credit rate per company with a worked example, the free repeat-within-an-hour idempotency, and the free estimate mode. It does not mention what happens on partial failure, rate limits, or errors when credits run out.

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?

Dense but front-loaded: price and key requirement come first, then the payload, then paging and cost caveats. Some phrasing is compressed to the point of being cryptic (e.g. 'the companies a count_companies question found'), but there is little 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?

For an 8-parameter, nested-filter, paid, non-read-only tool with no output schema, it covers cost, key, paging, returned fields, and the free preview — the things an agent must know before calling. The remaining gap is that it never explains how filters relate to a prior count_companies call or what happens when both filters and cursor are supplied.

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 100%, so baseline is 3. The description usefully restates the allowed limit values and explains the cursor as 'the next ones' into the same list, but it is silent on the large nested filters object, which is the dominant parameter and the main source of usage risk.

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?

States a specific verb plus resource — loading a paid set of companies into a company list in ListPlus — and enumerates the delivered fields (name, domain, website, industry, size, place, LinkedIn page). It also anchors itself to the sibling count_companies, making the read/count vs paid-deliver distinction obvious without opening a schema.

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 clear context: it delivers the companies a count_companies question found, and estimate:true is the free way to preview price without running anything. It does not explicitly say 'call count_companies first' or state when to prefer paging with cursor versus starting a new list, so the routing is implied rather than spelled out.

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?