boldsign

Instructions

Implementation Reference

• src/tools/documentsTools/listTeamDocuments.ts:100-126 (handler)

  The handler function that executes the core logic of the 'list_team_documents' tool by calling the BoldSign DocumentApi.teamDocuments method with filtered parameters and handling the MCP response or error.
  async function listTeamDocumentsHandler(payload: ListTeamDocumentsSchemaType): Promise<McpResponse> { try { const documentApi = new DocumentApi(); documentApi.basePath = configuration.getBasePath(); documentApi.setApiKey(configuration.getApiKey()); const teamDocumentRecords: TeamDocumentRecords = await documentApi.teamDocuments( payload.page, payload.userId ?? undefined, payload.teamId ?? undefined, (payload.transmitType as any) ?? undefined, payload.dateFilterType ?? undefined, payload.pageSize ?? undefined, payload.startDate ?? undefined, payload.status ?? undefined, payload.endDate ?? undefined, payload.searchKey ?? undefined, payload.labels ?? undefined, payload.nextCursor ?? undefined, payload.brandIds ?? undefined, ); return handleMcpResponse({ data: teamDocumentRecords, }); } catch (error: any) { return handleMcpError(error); } }
• src/tools/documentsTools/listTeamDocuments.ts:9-85 (schema)

  Zod schema defining the input validation for the 'list_team_documents' tool parameters including pagination, filters for users, teams, dates, status, etc.
  const ListTeamDocumentsSchema = z.object({ pageSize: z.number().int().min(1).max(100), page: z.number().int().min(1).default(1), searchKey: commonSchema.OptionalStringSchema.describe( 'Optional. A search term used to filter the document list. The API will return documents matching details like document title, document ID, sender name, or recipient name.', ), userId: z .array(commonSchema.InputIdSchema.describe('The unique identifier (ID) of a user in the team.')) .optional() .nullable() .describe( 'Optional. Filter documents based on the list of team member IDs. One or more user IDs can be specified.', ), teamId: z .array(commonSchema.InputIdSchema.describe('The unique identifier (ID) of the team.')) .optional() .nullable() .describe('Optional. Filter documents based on specific teams. One or more team IDs can be specified.'), startDate: commonSchema.OptionalDateSchema.describe( 'Optional. Start transmit date range of the document. The date should be in a valid date-time format.', ), endDate: commonSchema.OptionalDateSchema.describe( 'Optional. End transmit date range of the document. The date should be in a valid date-time format.', ), labels: z .array(z.string().describe('Label of the document.')) .optional() .nullable() .describe( 'Optional. Labels associated with documents. Used to filter the list by specific document tags.', ), transmitType: z .enum(['Sent', 'Received', 'Both']) .optional() .nullable() .default('Both') .describe("Optional. Type of transmission. Can be 'Sent', 'Received', or 'Both'."), status: z .array( z .enum([ 'None', 'WaitingForMe', 'WaitingForOthers', 'NeedAttention', 'Completed', 'Declined', 'Revoked', 'Expired', 'Scheduled', 'Draft', ]) .default('None'), ) .optional() .nullable() .describe( "Optional. Filter documents based on their current status. Available statuses include 'WaitingForMe', 'WaitingForOthers', 'NeedAttention', 'Completed', 'Declined', 'Revoked', 'Expired', 'Scheduled', and 'Draft'. Use 'None' to disable status filtering.", ), nextCursor: commonSchema.OptionalIntegerSchema.describe( 'Optional. Cursor value for pagination beyond 10,000 records. Set to the cursor of the last retrieved document.', ), brandIds: z .array(commonSchema.InputIdSchema.describe('Unique identifier (ID) of the brand.')) .optional() .nullable() .describe( 'Optional. Filters documents based on associated brand IDs. Only documents linked to the specified brands will be retrieved.', ), dateFilterType: z .enum(['SentBetween', 'Expiring']) .optional() .nullable() .describe( "Optional. Type of date filter applied to documents. Available options: 'SentBetween' and 'Expiring'.", ), });
• src/tools/documentsTools/listTeamDocuments.ts:89-98 (registration)

  The tool definition that registers 'list_team_documents' with its method name, description, input schema, and handler wrapper. This is exported and included in higher-level tool arrays.
  export const listTeamDocumentsToolDefinition: BoldSignTool = { method: ToolNames.ListTeamDocuments.toString(), name: 'List team documents', description: 'Retrieve a paginated list of documents available in the Team Documents section of your BoldSign organization. Team admins can view documents sent and received by team members, while account admins have access to all team documents across the organization. This API allows filtering based on status, user ID, team ID, document details, transmission type, and date range. If the user is not an account admin or team admin, an unauthorized response will be returned.', inputSchema: ListTeamDocumentsSchema, async handler(args: unknown): Promise<McpResponse> { return await listTeamDocumentsHandler(args as ListTeamDocumentsSchemaType); }, };