Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

by Synctest-hub

list_teams

Retrieve and manage teams in your BoldSign organization. View team details like name, members, and dates, with search and pagination options.

Instructions

Retrieve a paginated list of teams within your BoldSign organization. This API fetches team details such as team name, users, created date, and modified date for all listed teams, with options for filtering using a search term and navigating through pages of results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeYes
pageYes
searchKeyNoOptional. A search term to filter the list of teams. The API will return teams whose details, such as name, match the provided search term.

Implementation Reference

  • The main handler function that implements the list_teams tool. It initializes the TeamsApi client, calls listTeams with pagination and search parameters, and handles the response or errors using utility functions.
    async function listTeamsHandler(payload: ListTeamsSchemaType): Promise<McpResponse> {
      try {
        const teamsApi = new TeamsApi();
        teamsApi.basePath = configuration.getBasePath();
        teamsApi.setApiKey(configuration.getApiKey());
        const teamListResponse: TeamListResponse = await teamsApi.listTeams(
          payload.page,
          payload.pageSize ?? undefined,
          payload.searchKey ?? undefined,
        );
        return handleMcpResponse({
          data: teamListResponse,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod schema defining the input parameters for the list_teams tool: pageSize (1-100), page (default 1), optional searchKey.
    const ListTeamsSchema = 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 to filter the list of teams. The API will return teams whose details, such as name, match the provided search term.',
      ),
    });
    
    type ListTeamsSchemaType = z.infer<typeof ListTeamsSchema>;
  • Tool definition registering the 'list_teams' tool, including name, description, input schema, and wrapper handler that delegates to listTeamsHandler.
    export const listTeamsToolDefinition: BoldSignTool = {
      method: ToolNames.ListTeams.toString(),
      name: 'List teams',
      description:
        'Retrieve a paginated list of teams within your BoldSign organization. This API fetches team details such as team name, users, created date, and modified date for all listed teams, with options for filtering using a search term and navigating through pages of results.',
      inputSchema: ListTeamsSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await listTeamsHandler(args as ListTeamsSchemaType);
      },
    };
  • Registers the listTeamsToolDefinition in the array of teams API tools, which is later aggregated into the main tools list.
    export const teamsApiToolsDefinitions: BoldSignTool[] = [getTeamToolDefinition, listTeamsToolDefinition];
  • Enum definition providing the exact string name 'list_teams' used in the tool method.
     * Retrieve a paginated list of teams within your BoldSign organization.
     * This API fetches team details such as team name, users, creation date, and modification date for all listed teams,
     * with options for filtering using a search term and navigating through pages of results.
     */
    ListTeams = 'list_teams',

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.1/5.0
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 capability via search term, and what data is returned (team name, users, dates). However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens when no teams match the search term.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two well-structured sentences that efficiently convey purpose, scope, capabilities, and parameters. The first sentence establishes core functionality, the second adds details about returned data and parameter usage. Every element earns its place with zero wasted words.

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 3 parameters and no output schema, the description covers the essential 'what' and 'how' but has gaps. It explains pagination and filtering but doesn't describe the return format structure, error handling, or authentication context. Given the lack of annotations and output schema, more behavioral detail would be helpful.

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 33% (only 'searchKey' has a description). The description compensates by explaining the purpose of pagination ('navigating through pages of results') and filtering ('options for filtering using a search term'), which adds meaningful context beyond the bare schema. It doesn't detail parameter constraints like pageSize limits, but provides good semantic value.

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'), resource ('teams within your BoldSign organization'), and scope ('all listed teams'). It distinguishes from sibling tools like 'get_team' (singular) and 'list_contacts' (different resource) by explicitly focusing on teams with pagination and filtering capabilities.

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 get a comprehensive, paginated list of teams with optional filtering. It doesn't explicitly state when not to use it or name alternatives, but the context implies this is for bulk retrieval rather than single-team lookup (which would use 'get_team').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.