Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

by Synctest-hub

list_users

Retrieve a paginated list of BoldSign users with optional search filtering to manage e-signature platform access and permissions.

Instructions

Retrieves a paginated list of BoldSign users, with optional filtering by a search term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeYes
pageYes
searchNoOptional. A string used to filter the user list. The API will return contacts whose details contain this search term.

Implementation Reference

  • Executes the list_users tool by creating a UserApi instance, configuring it, calling the BoldSign API's listUsers method with pagination and search parameters, and handling the response or error.
    async function listUsersHandler(payload: ListUsersSchemaType): Promise<McpResponse> {
      try {
        const userApi = new UserApi();
        userApi.basePath = configuration.getBasePath();
        userApi.setApiKey(configuration.getApiKey());
        const userRecords: UserRecords = await userApi.listUsers(
          payload.page,
          payload.pageSize ?? undefined,
          payload.search ?? undefined,
        );
        return handleMcpResponse({
          data: userRecords,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod schema for validating input to the list_users tool: pageSize (1-100), page (default 1), optional search string.
    const ListUsersSchema = z.object({
      pageSize: z.number().int().min(1).max(100),
      page: z.number().int().min(1).default(1),
      search: commonSchema.OptionalStringSchema.describe(
        'Optional. A string used to filter the user list. The API will return contacts whose details contain this search term.',
      ),
    });
  • Tool definition object for 'list_users', specifying method name, description, input schema, and wrapper handler calling the main listUsersHandler.
    export const listUsersToolDefinition: BoldSignTool = {
      method: ToolNames.ListUsers.toString(),
      name: 'List users',
      description: 'Retrieves a paginated list of BoldSign users, with optional filtering by a search term.',
      inputSchema: ListUsersSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await listUsersHandler(args as ListUsersSchemaType);
      },
    };
  • Collects and exports users API tools definitions, including listUsersToolDefinition, as an array.
    import { getUserToolDefinition } from '../../tools/usersTools/getUser.js';
    import { listUsersToolDefinition } from '../../tools/usersTools/listUsers.js';
    import { BoldSignTool } from '../../utils/types.js';
    
    export const usersApiToolsDefinitions: BoldSignTool[] = [getUserToolDefinition, listUsersToolDefinition];
  • Imports users API tools and includes them in the central definitions array used for MCP tool registration.
    import { usersApiToolsDefinitions } from './usersTools/index.js';
    
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only mentions pagination and optional filtering. It lacks details on permissions, rate limits, error handling, or what fields are returned. For a read operation with 3 parameters, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads key information (retrieval, pagination, filtering). It avoids redundancy but could be slightly more structured (e.g., separating core purpose from optional features).

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?

For a tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't cover return values, error cases, or behavioral nuances like pagination mechanics. Given the complexity, it should provide more context to be complete.

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 description coverage is low (33%), with only the 'search' parameter documented. The description adds that filtering is by 'search term', but doesn't explain 'pageSize' or 'page' beyond what the schema provides (e.g., ranges). It partially compensates but not fully for the coverage gap.

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 action ('Retrieves') and resource ('BoldSign users'), and specifies it's a paginated list with optional filtering. However, it doesn't explicitly differentiate from sibling tools like 'get_user' (singular) or 'list_contacts', leaving some ambiguity about scope.

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 like 'get_user' (for single user) or 'list_contacts'. The description mentions optional filtering but doesn't clarify use cases or prerequisites, offering minimal contextual direction.

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