Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

list_contacts

Retrieve and filter contacts from your BoldSign organization to manage signer details for document workflows. Supports pagination and search by contact type.

Instructions

This tool allows you to retrieve a paginated list of contacts from your BoldSign organization. You can specify the page number to navigate through the results, the number of contacts to display per page, an optional search term to filter contacts, and the type of contacts to retrieve (your personal contacts or all organizational contacts). Contacts are primarily used to store signer details, identified by their unique email address, for use when creating and sending documents for signature within the BoldSign application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeYes
pageYes
searchKeyNoOptional. A string used to filter the contact list. The API will return contacts whose details contain this search term.
contactTypeYesOptional. Filters the list of contacts based on their type. 'MyContacts' retrieves contacts specifically associated with your account, while 'AllContacts' (default) retrieves all accessible contacts within your organization.AllContacts

Implementation Reference

  • The main handler function that instantiates the BoldSign ContactsApi, calls the contactUserList method with paginated and filtered parameters, and returns the response or handles errors using utility functions.
    async function listContactsHandler(payload: ListContactsSchemaType): Promise<McpResponse> {
      try {
        const contactsApi = new ContactsApi();
        contactsApi.basePath = configuration.getBasePath();
        contactsApi.setApiKey(configuration.getApiKey());
        const contactsList: ContactsList = await contactsApi.contactUserList(
          payload.page,
          payload.pageSize ?? undefined,
          payload.searchKey ?? undefined,
          payload.contactType ?? undefined,
        );
        return handleMcpResponse({
          data: contactsList,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod input schema for the list_contacts tool, defining parameters: pageSize (1-100), page (default 1), optional searchKey, and contactType (MyContacts or AllContacts, default AllContacts).
    const ListContactsSchema = z.object({
      pageSize: z.number().int().min(1).max(100),
      page: z.number().int().min(1).default(1),
      searchKey: commonSchema.OptionalStringSchema.describe(
        'Optional. A string used to filter the contact list. The API will return contacts whose details contain this search term.',
      ),
      contactType: z
        .enum(['MyContacts', 'AllContacts'])
        .optional()
        .nullable()
        .default('AllContacts')
        .describe(
          "Optional. Filters the list of contacts based on their type. 'MyContacts' retrieves contacts specifically associated with your account, while 'AllContacts' (default) retrieves all accessible contacts within your organization.",
        ),
    });
  • Tool definition object that registers the list_contacts tool with MCP, specifying the method name, description, input schema, and a wrapper handler that delegates to the main handler.
    export const listContactsToolDefinition: BoldSignTool = {
      method: ToolNames.ListContacts.toString(),
      name: 'List contacts',
      description:
        'This tool allows you to retrieve a paginated list of contacts from your BoldSign organization. You can specify the page number to navigate through the results, the number of contacts to display per page, an optional search term to filter contacts, and the type of contacts to retrieve (your personal contacts or all organizational contacts). Contacts are primarily used to store signer details, identified by their unique email address, for use when creating and sending documents for signature within the BoldSign application.',
      inputSchema: ListContactsSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await listContactsHandler(args as ListContactsSchemaType);
      },
    };
  • Exports an array of contacts API tool definitions, including the list_contacts tool, which is then included in higher-level tool registries.
    export const contactsApiToolsDefinitions: BoldSignTool[] = [
      getContactToolDefinition,
      listContactsToolDefinition,
    ];
  • Enum definition providing the string identifier 'list_contacts' used as the tool method name.
    /**
     * This tool allows you to retrieve a paginated list of contacts from your BoldSign organization.
     * You can specify the page number to navigate through the results, the number of contacts to display per page,
     * an optional search term to filter contacts, and the type of contacts to retrieve (your personal contacts or all organizational contacts).
     * Contacts are primarily used to store signer details, identified by their unique email address,
     * for use when creating and sending documents for signature within the BoldSign application.
     */
    ListContacts = 'list_contacts',
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: pagination behavior, filtering capabilities, and contact types. However, it doesn't mention authentication requirements, rate limits, error conditions, or what the response structure looks like (though there's no output schema).

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 appropriately sized with two focused sentences. The first sentence efficiently covers the core functionality and all parameters. The second provides valuable context about contact usage. There's minimal redundancy, though the structure could be slightly more front-loaded.

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?

For a read-only list tool with 4 parameters and no output schema, the description provides adequate coverage of what the tool does and its parameters. However, without annotations or output schema, it lacks details about authentication, error handling, response format, and explicit sibling tool differentiation that would make it more complete.

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?

Schema description coverage is only 50% (2 of 4 parameters have descriptions). The description compensates well by explaining all four parameters' purposes: page navigation, results per page, search filtering, and contact type selection. It adds meaningful context beyond what little schema documentation exists.

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 the tool's purpose with specific verbs ('retrieve', 'display', 'filter') and resources ('paginated list of contacts from your BoldSign organization'). It distinguishes itself from sibling tools like 'get_contact' by focusing on listing multiple contacts rather than retrieving a single one, and from other list tools by specifying the contact domain.

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 provides clear context for when to use this tool: to retrieve contacts for use in document signing workflows. It implicitly distinguishes from 'get_contact' by handling lists vs. single contacts, but doesn't explicitly state when to choose this over alternatives like 'list_users' 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.

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