cursor-api-mcp

sync_organization_team_memberships

Synchronize organization users with their team memberships by submitting a JSON array of user IDs and target team IDs.

Instructions

Sync org users onto linked teams (POST /organizations/team-memberships/sync).

Requires Organization API key with members:* (or admin:*).

Args: organization_id: Public org id (org_...). users_json: JSON array of {userId, teamIds[]} or {userId, destinationTeamId} entries.

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": {
      "organization_id": "<organization_id>",
      "users_json": "<users_json>"
    },
    "name": "sync_organization_team_memberships"
  }
}

Input Schema

Name	Required	Description	Default
`users_json`	Yes
`organization_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided; description mentions it is a POST operation requiring permissions but does not disclose if it overwrites or merges team memberships, or any side effects.

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 lines with no unnecessary words, front-loaded with purpose, and efficiently conveys endpoint, permissions, and argument details.

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?

Has an output schema so return values are covered, but lacks behavioral details like whether sync is incremental or full, and does not explain the string option for users_json.

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?

Provides meaning for both parameters: organization_id is a public org ID with format hint, and users_json is a JSON array of specific structures. However, it does not clarify the anyOf allowing string, leaving ambiguity.

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 it syncs org users onto linked teams, includes the HTTP method and path, and is distinct from sibling tools like list_organization_members or add_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 Guidelines4/5

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

Specifies required API key permissions and the format of users_json, but does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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

Deploy Server