Skip to main content
Glama

Remove a project from a list

remove_from_list
DestructiveIdempotent

Removes one project from a membership list, including merge-family rows. Does not use credits.

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>",
      "projectId": "<projectId>"
    },
    "name": "remove_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list's public id ("lst_…"), from list_user_lists.
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description earns credit for adding two pieces of non-obvious context: it also removes merge-family rows, and the operation costs no credits. It omits what happens on a non-member project (silent no-op vs error), which is the main remaining behavioral question for an idempotent destructive call.

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?

Two short sentences, front-loaded with the core action and scope, followed by the cost note. Nothing is redundant with the title or the annotations.

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-read-only mutation with rich annotations and no output schema, the definition covers scope, side effects on merge-family rows, and cost. The gaps are error behavior and permission requirements, both of which matter for a destructive operation but are secondary for a tool this simple.

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 only 50%: listId is well documented (public id format plus a pointer to list_user_lists) while projectId carries no description at all. The description does clarify that exactly one project is affected, reinforcing that projectId is a single identifier rather than a collection, but it adds nothing about the listId or the expected id format.

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?

The description names a specific verb and resource ("removes one project from a membership list"), which distinguishes it from add_to_list and from the list-reading siblings such as get_list or list_user_lists. It stops short of naming its nearest sibling remove_permit_from_list, but the object being removed (a project) is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no statement of prerequisites, such as whether the project must already be a member or the list must exist. The closest thing to guidance is the scope word "one", which implies this is the single-item variant, but the agent must infer that.

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