Skip to main content
Glama

minari_list

Contact lists — the call lists reps work through.

SCOPE WARNING: these endpoints see the CSV-import source ONLY. A company whose contacts come from HubSpot or Salesforce has real lists that never appear here, so an empty result means "no CSV list", not "no list". The all-sources view is minari_analytics(op="lists").

"create" is how you push a prospecting list into the dialer: build the contacts elsewhere, assign the list to a rep, and it appears in their Minari. A contact already known to the account is ADDED to the list rather than duplicated; its stored fields stay untouched unless update_existing_contacts=True (a blank value never overwrites).

A list holds at most 1500 contacts, and at most 1500 can be sent per request.

"delete" is PERMANENT and takes the list's contacts out of the rep's queue. It cannot be undone from this tool or from Minari.

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": "minari_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNo"list" browses lists; "get" is one list with its contacts; "create" makes a list and imports contacts; "delete" destroys a list permanently.list
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
nameNoREQUIRED by "create" — the list name (255 chars max).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
cursorNo"list" only — `next_cursor` from a previous response; it is a position, not a saved query.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
list_idNoREQUIRED by "get" and "delete".
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
contactsNoREQUIRED by "create" — up to 1500 objects. Each needs at least one of `firstName`, `lastName`, `email`. Also accepts `company`, `title`, `companyDomain`, `linkedinUrl`, `description`, `phoneNumber1`…`phoneNumber5`, `note` (5000 chars, attached as a note), and `customFields` keyed by ids registered through `minari_custom_field`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
assigned_toNoREQUIRED by "create" — the team member id that will own the list, from `minari_user`.
max_contactsNo"get" only — cap on contacts returned (default 100). A list returns all 1500 at once otherwise; the response states the true total and whether it was truncated.
update_existing_contactsNo"create" only — overwrite stored fields of contacts that already exist. Defaults to false.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the CSV-only data source, dedupe behavior on import (existing contacts are ADDED not duplicated, stored fields untouched unless update_existing_contacts=True, blanks never overwrite), the 1500-contact list cap and 1500-per-request send cap, and that delete is irreversible from this tool or from Minari. These are non-obvious behaviors that go well beyond the op names.

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?

Front-loaded with the resource definition and scope warning, then organized by operation with the destructive one flagged in caps. For a four-op tool this length is justified and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers the remaining complexity: source scope, import dedupe rules, size limits, and irreversibility of delete. An agent has everything needed to choose the op and predict its effects.

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 genuinely adds semantics the schema does not: the dedupe/overwrite interaction for the contacts parameter and the per-request 1500 cap that constrains it. It does not elaborate on the routing parameters (_org, _project, _run_id), though those are fully documented in the schema.

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 opening line defines the resource concretely ("Contact lists — the call lists reps work through") and the body describes what each of the four ops does, including that "create" pushes a prospecting list into the dialer. It also names the sibling that gives the all-sources view, `minari_analytics(op="lists")`, so an agent can distinguish the two without opening either schema.

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?

Provides an explicit SCOPE WARNING telling the agent when this tool's results are misleading ("an empty result means 'no CSV list', not 'no list'") and names the alternative tool to use instead. It also prescribes the create workflow (build contacts elsewhere, assign to a rep) and warns that delete is permanent, which is exactly the when/when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources