Skip to main content
Glama

list_contacts

Retrieve a paginated list of contacts from your BoldSign organization to access signer details for document signing workflows. Filter by search terms and 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 primary handler function for the 'list_contacts' tool. It initializes the BoldSign ContactsApi client, calls the contactUserList API with provided pagination, search, and contact type parameters, processes the response, and handles any errors.
    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 validating parameters of the list_contacts tool: pageSize (1-100), page (default 1), optional searchKey, 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 registration definition for 'list_contacts'. Specifies the method name, human-readable name and description, references the input schema, and provides a wrapper handler that casts arguments and delegates to the main handler function.
    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);
      },
    };
  • Local registration of list_contacts tool as part of the contacts API tools array, alongside getContact.
    export const contactsApiToolsDefinitions: BoldSignTool[] = [
      getContactToolDefinition,
      listContactsToolDefinition,
    ];
  • Global registration where contacts API tools (including list_contacts) are spread into the master list of all BoldSign tool definitions.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
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 pagination behavior and contact usage context, but lacks details on authentication requirements, rate limits, error conditions, or response format. It adequately describes the core operation but misses important behavioral traits for a read 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?

Two well-structured sentences: first covers core functionality and parameters, second provides business context. Slightly verbose with 'allows you to' phrasing, but each sentence adds value. Could be more front-loaded by leading with the primary purpose.

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 4-parameter read tool with no annotations and no output schema, the description provides adequate purpose and parameter context but lacks critical behavioral details like response structure, error handling, and authentication. It's minimally viable but has clear gaps in completeness.

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 50% (only searchKey and contactType have descriptions). The description compensates by explaining all four parameters: page navigation, per-page display, search filtering, and contact type distinction. It adds meaningful context beyond the schema, though doesn't specify exact search behavior or default values.

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 specific action ('retrieve a paginated list of contacts'), resource ('from your BoldSign organization'), and scope ('contacts are primarily used to store signer details... for use when creating and sending documents for signature'). It distinguishes from siblings like 'get_contact' (singular) and 'list_documents' (different resource).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving contacts for document signing workflows, but lacks explicit guidance on when to use this versus alternatives like 'get_contact' (for single contact) or 'list_users' (different resource). No when-not-to-use scenarios or prerequisites are mentioned.

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

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