cursor-api-mcp

list_organization_members

Retrieve a paginated list of members in your organization. Use page and page_size parameters to control results.

Instructions

List organization members (GET /organizations/members).

Works with an Organization API key scoped to members:read (or broader).

Args: page: 1-indexed page (default 1). page_size: Members per page, capped at 200 (default 50).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_organization_members"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`page_size`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must disclose behavior. It specifies the GET method and API key scope, and notes page_size cap of 200. It does not mention rate limits, side effects, or return format, but output schema covers return structure. Acceptable but not rich.

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?

The description is extremely concise with only three sentences and a compact args list. Every sentence adds value, and the structure prioritizes key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to detail return values. It covers basic usage and parameters, but lacks mention of ordering, filtering, or any other behavior. Adequate but not comprehensive.

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

Parameters4/5

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

Schema coverage is 0%, so description carries the burden. It explains page is 1-indexed with default 1, page_size capped at 200 with default 50. This adds meaningful context beyond the schema's default values.

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 clearly states the tool lists organization members and provides the HTTP endpoint. However, it does not differentiate from sibling tools like list_organization_group_members, which could cause confusion.

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

Usage Guidelines3/5

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

The description mentions required API key scope (members:read or broader), giving context on when to use. It lacks explicit when-not-to-use or alternatives, but the scope hint is helpful.

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

Deploy Server