Skip to main content
Glama

Add new people to a list

add_people_to_list

Use this when the user has people of their own to put on a people list, described by what is known about them: each needs at least one of email, linkedinUrl, firstName and lastName. Adds up to 500 people in one call. Nothing is looked up or checked, and an email address is kept as sent. Every row becomes a new person, even one already in the workspace, so calling again adds the same people a second time. Company lists are refused. Free.

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": {
      "listId": "<listId>",
      "rows": "<rows>"
    },
    "name": "add_people_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesThe people to add, at most 500. Each row becomes a new person, even one already in the workspace.
listIdYesThe list's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, idempotent=false, destructive=false) by disclosing that nothing is validated or enriched, that emails are stored verbatim, that every row creates a new person even if one already exists, that repeat calls duplicate, and that the call is free. These are exactly the non-obvious consequences an agent needs before invoking a non-idempotent write.

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-loads the trigger, then packs validation behavior, idempotency warnings, list-type exclusions and cost into short declarative clauses with no filler. The one-word 'Free.' sentence still carries unique information not present elsewhere.

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 two-parameter write with no output schema and full schema coverage, it covers nearly everything an agent needs: preconditions, dedup behavior, size cap and refusal cases. The only gap is what a call returns (created IDs, partial failures, or a count), which the agent must discover on its own.

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 coverage is 100% and the description largely restates structured data (the 500 max and the 'at least one of email, linkedinUrl, firstName, lastName' rule are both already in the schema). It adds only the framing 'described by what is known about them', so the baseline of 3 is appropriate.

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 precise verb and resource ('Adds up to 500 people' to 'a people list') and scopes the input as 'people of their own... described by what is known about them', which implicitly separates it from copy_people_to_list and add_people_to_campaign. The note that 'Company lists are refused' further pins down which list type applies.

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?

Opens with an explicit trigger ('Use this when the user has people of their own to put on a people list') and adds a hard exclusion ('Company lists are refused'). It also warns that repeat calls duplicate rows, which steers the agent away from naive retries, but it never names the sibling tool it should use instead when the people already exist in the workspace.

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