Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get-users

Read-onlyIdempotent

Fetch workspace users by specific IDs, or search by name or email. Returns the full user list when no filters are provided.

Instructions

Get users from a workspace. Retrieves all workspace users by default, or specific users if userIds array is provided. Supports optional case-insensitive search filtering by name or email.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "get-users"
  }
}

Input Schema

Name	Required	Description
`userIds`	No	Optional array of specific user IDs to fetch. If not provided or empty array, fetches all workspace users.
`searchText`	No	Optional search text to filter users by name or email (case-insensitive).
`workspaceId`	Yes	The workspace ID to get users from.

Output Schema

Name	Required	Description	Default
`type`	Yes
`users`	Yes
`totalUsers`	Yes
`workspaceId`	Yes
`filteredUsers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv7.0.0Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv5.5.1Jul 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds useful behavioral context such as the default fallback to all workspace users and case-insensitive filtering by name or email. It does not mention edge cases like empty arrays, pagination, or invalid IDs, but the annotations cover the safety profile.

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 three short sentences with no filler. It front-loads the core purpose and then adds default behavior and filtering details efficiently. Every sentence earns its place.

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

Completeness5/5

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

Given that this is a read-only lookup tool with full schema descriptions and an output schema available, the description covers the essential behavior completely. Nothing critical for correct invocation is missing.

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%, and every parameter already has a meaningful description. The tool description mostly restates the parameter behavior rather than adding new semantic detail, so the baseline score of 3 is appropriate.

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 a specific verb and resource: get users from a workspace. It also explains the default full-list behavior and optional filtering, which makes the tool's purpose easy to identify, though it does not explicitly contrast it with the user-info sibling tool.

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?

The description gives clear context for when to use the tool: fetch all workspace users, fetch specific users by ID, or filter by case-insensitive search text. It does not name alternatives or state when not to use it, but the intended call patterns are explicit.

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