Skip to main content
Glama

Remove people from a list

remove_people_from_list
DestructiveIdempotent

Use this when the user wants people taken off a list, by id, up to 5,000 in one call. They stay in the workspace and on their other lists. An id that is not on the list is skipped. 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>",
      "personIds": "<personIds>"
    },
    "name": "remove_people_from_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 destructiveHint=true and idempotentHint=true, but the description adds what the annotations cannot: the destruction is scoped to list membership only, since people 'stay in the workspace and on their other lists'. It also discloses the skip-not-error behavior for ids not on the list and that the call is free, which is real context beyond the structured fields. Response shape and auth requirements are still unstated.

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?

Three short sentences, front-loaded with the use case, then scope, then edge-case behavior, with the cost note compressed to a single word. Nothing is redundant or buried.

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 mutation tool with no output schema, the definition covers trigger, blast radius, skip semantics and cost, which is most of what an agent needs. It stops short of saying what the call returns (e.g. counts of removed versus skipped ids) and what happens if listId does not exist.

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%, with both parameters carrying patterns, bounds and examples, so the schema already does the heavy lifting. The description's 'up to 5,000 in one call' restates maxItems, and 'by id' restates the property name; only the 'skipped' note adds semantics, and that applies to outcomes rather than parameter 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 verb and resource ('people taken off a list, by id') with a clear batch bound of 5,000 per call, which separates it from the add/copy siblings. It does not contrast itself with the nearby but distinct exclusion concept (exclude_list), so the differentiation is good rather than airtight.

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 wants people taken off a list'. That is clear when-to-use guidance. There is no when-not clause and no named alternative for cases like full list deletion (delete_list) or global suppression (exclude_list).

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