Skip to main content
Glama

Add saved people to a list

copy_people_to_list
Idempotent

Use this when people who are already in the workspace should also be on another list. Send their ids, up to 5,000 in one call: the id of their row on a list, or the ids an earlier upload answered with. People already on the list are skipped, so calling again adds nobody twice. Free. It creates no new people.

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>",
      "personIds": "<personIds>"
    },
    "name": "copy_people_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list's id.
personIdsYesPeople's ids, at most 5,000: the `id` of their rows in another list, or the `personIds` an upload answered with.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description goes further by explaining the mechanism ('People already on the list are skipped, so calling again adds nobody twice') and adding cost ('Free') and side-effect scope ('creates no new people'). Permissions, rate limits, and any partial-failure behavior are still unstated, which is normal against such strong annotations.

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?

Four short sentences, front-loaded with the usage condition, then batching, then dedupe behavior, then the negative scope. No filler, and even the one-word 'Free.' earns its place as a cost signal.

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, non-destructive, idempotent write tool with no output schema, the description covers when to use it, the id source, the batch cap, dedupe semantics, cost, and the no-creation guarantee. Only the response shape and per-list limits are absent, which are minor given the tool's simplicity.

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 schema's own descriptions already explain that personIds are row ids from another list or ids returned by an upload. The description's 'the id of their row on a list, or the ids an earlier upload answered with' essentially restates that, and the 5,000 cap is likewise in the schema, so it adds little new meaning.

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?

States a specific action (putting already-saved people onto another list) and scopes it negatively with 'It creates no new people,' which separates it from person-creation flows. However, it never names the close sibling add_people_to_list, so an agent must infer the copy-vs-add distinction rather than being told it.

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?

'Use this when people who are already in the workspace should also be on another list' gives a concrete triggering condition, and the closing 'creates no new people' implicitly steers creation to a different tool. No alternative is named explicitly and no when-not-to-use exclusion is stated, so it stops short of full routing guidance.

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