Skip to main content
Glama
Sign In
cursor-api-mcp

cursor-api-mcp

by PhillipChaffee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_organization_group_members

Remove members from an organization group. Specify the group ID and a JSON array of user IDs (up to 100 per request).

Instructions

Remove members from an org group (POST .../members/bulk-remove).

Args: group_id: Organization group id (g_...). user_ids_json: JSON array of user ids (max 100 per request).

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": {
      "group_id": "<group_id>",
      "user_ids_json": "<user_ids_json>"
    },
    "name": "remove_organization_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes
user_ids_jsonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries burden. It discloses HTTP method (POST), bulk operation, and max 100 users per request. This adds meaningful behavioral context beyond the tool name.

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?

Extremely concise: two sentences plus a structured argument list. No redundant words. Every sentence adds value.

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?

Given an output schema exists, the description need not explain return values. It covers the HTTP method, parameter formats, and limits. Could mention idempotency or error handling, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description compensates fully: it explains group_id format (g_...) and clarifies user_ids_json as a JSON array with a max limit. This adds significant meaning beyond the schema's type info.

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 description clearly states the action ('Remove members') and the resource ('from an org group'). It distinguishes from sibling tools like add_organization_group_members and list_organization_group_members.

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?

No guidance on when to use this tool versus alternatives (e.g., when to remove vs. leave?). Implied usage only. No exclusions or prerequisites mentioned.

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

Deploy Server

Other Tools