Skip to main content
Glama

list_team_documents

Retrieve and filter team documents in BoldSign by status, user, team, date range, or search terms to manage organizational document workflows.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeYes
pageYes
searchKeyNoOptional. 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.
userIdNoOptional. Filter documents based on the list of team member IDs. One or more user IDs can be specified.
teamIdNoOptional. Filter documents based on specific teams. One or more team IDs can be specified.
startDateNoOptional. Start transmit date range of the document. The date should be in a valid date-time format.
endDateNoOptional. End transmit date range of the document. The date should be in a valid date-time format.
labelsNoOptional. Labels associated with documents. Used to filter the list by specific document tags.
transmitTypeYesOptional. Type of transmission. Can be 'Sent', 'Received', or 'Both'.Both
statusNoOptional. 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.
nextCursorNoOptional. Cursor value for pagination beyond 10,000 records. Set to the cursor of the last retrieved document.
brandIdsNoOptional. Filters documents based on associated brand IDs. Only documents linked to the specified brands will be retrieved.
dateFilterTypeNoOptional. Type of date filter applied to documents. Available options: 'SentBetween' and 'Expiring'.

Implementation Reference

  • The core handler function that executes the tool logic 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);
      }
    }
  • Zod schema defining the input parameters for the list_team_documents tool, including pagination, filters for users, teams, dates, status, labels, 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'.",
        ),
    });
  • Tool definition exporting the tool with method name 'list_team_documents', description, schema, and a wrapper handler that delegates to the main handler.
    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);
      },
    };
  • Registration of the tool definition in the documents API tools array.
    export const documentsApiToolsDefinitions: BoldSignTool[] = [
      getDocumentPropertiesToolDefinition,
      listDocumentsToolDefinition,
      listTeamDocumentsToolDefinition,
      sendReminderForDocumentToolDefinition,
      revokeDocumentToolDefinition,
    ];
  • Final registration where documentsApiToolsDefinitions (including list_team_documents) is spread into the main tools definitions array.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes access control (admin roles required), pagination behavior, filtering capabilities, and error conditions (unauthorized response). However, it lacks details on rate limits, response format, or what happens with large result sets beyond pagination.

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 and front-loaded with the core purpose. Every sentence adds value: first states what it does, second explains access levels, third details filtering, fourth specifies authorization requirements. It could be slightly more concise by combining some filtering details, but overall structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (13 parameters, no output schema, no annotations), the description does well by covering purpose, access control, filtering, and error conditions. However, it lacks details about the return format (what fields documents have) and doesn't explain pagination mechanics beyond mentioning it's 'paginated,' which is a gap for a list tool with no output schema.

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 high at 85%, so the baseline is 3. The description adds value by summarizing the filtering capabilities ('filtering based on status, user ID, team ID, document details, transmission type, and date range'), but doesn't provide additional syntax or format details beyond what's already documented in the schema descriptions.

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 verb ('Retrieve'), resource ('paginated list of documents'), and scope ('Team Documents section of your BoldSign organization'). It distinguishes from siblings like 'list_documents' by specifying the team context and administrative access requirements, making the purpose specific and differentiated.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: for team documents with admin access (team admins view team member documents, account admins view all). It also provides exclusion criteria: 'If the user is not an account admin or team admin, an unauthorized response will be returned,' clearly indicating prerequisites and when not to use it.

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