Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

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,
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions pagination and filtering but doesn't disclose important behavioral traits: authentication requirements, rate limits, what 'details' the search term covers (name, email, etc.), default sorting, or error conditions. The description is insufficient for a mutation-free but potentially complex list operation.

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, well-structured sentence that efficiently conveys the core functionality. It's front-loaded with the main purpose and includes key modifiers. However, it could be slightly more concise by integrating the optional nature of filtering more smoothly.

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 list tool with 3 parameters, 33% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on authentication, rate limits, search scope, pagination behavior, error handling, and output format. The agent would struggle to use this tool correctly without additional context.

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 only 33% (only 'search' has a description). The description adds that filtering is 'optional' and by 'search term', which partially compensates but doesn't explain the semantics of 'pageSize' and 'page' parameters. It doesn't clarify what 'page' 1 represents or how pagination works with filtering.

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 verb ('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 'list_contacts' or 'get_user', which would require more specific scope clarification.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_user' (for single user) or 'list_contacts'. It mentions optional filtering but doesn't explain when filtering is appropriate or what the search term targets beyond 'details'.

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/Synctest-hub/boldsign-mcp'

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