Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

users-list

Retrieve all user accounts from Shortcut project management to access team member information for task assignment and collaboration.

Instructions

Get all users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the "users-list" tool. It fetches all members via the ShortcutClientWrapper's listMembers method and formats the result using the inherited toResult method.
    async listMembers() {
    	const members = await this.client.listMembers();
    
    	return this.toResult(`Found ${members.length} members:`, members);
    }
  • Registration of the "users-list" MCP tool within the static create method of UserTools class, which adds it to the CustomMcpServer.
    server.addToolWithReadAccess(
    	"users-list",
    	"Get all users",
    	async () => await tools.listMembers(),
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Get all users' implies a read-only operation, but doesn't disclose behavioral traits such as pagination, rate limits, authentication requirements, or what 'all' entails (e.g., active users only, includes deleted users). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 just three words, front-loading the core action and resource. There's no wasted language or unnecessary elaboration, making it easy to parse quickly. For a simple tool with no parameters, this brevity is effective.

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

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is minimal but incomplete. It lacks context about what 'all users' means, the return format, or any behavioral nuances. Without annotations or output schema, the description should provide more operational details to be fully helpful for an agent.

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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter details, but that's acceptable given the empty schema. A baseline of 4 is appropriate since there are no parameters to explain, and the description doesn't introduce confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all users' clearly states the verb ('Get') and resource ('users'), but lacks specificity about scope or format. It distinguishes from sibling tools like 'users-get-current' by implying retrieval of all users rather than just the current user, but doesn't explicitly differentiate from other list tools like 'teams-list' or 'workflows-list' beyond the resource name.

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 is provided on when to use this tool versus alternatives. While the name suggests it retrieves all users, there's no mention of prerequisites, limitations, or comparisons to other user-related tools like 'users-get-current' or 'users-get-current-teams'. The description alone doesn't help an agent decide between this and other list or get operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/useshortcut/mcp-server-shortcut'

If you have feedback or need assistance with the MCP directory API, please join our Discord server