Skip to main content
Glama
bucketeer-io

Bucketeer MCP Server

Official
by bucketeer-io

listFeatureFlags

Retrieve all feature flags from a Bucketeer environment with filtering, pagination, and search options to manage feature rollouts.

Instructions

List all feature flags in the specified environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentIdNoEnvironment ID (uses default if not provided)
pageSizeNoNumber of items per page (1-100)
cursorNoPagination cursor for next page
tagsNoFilter by tags
orderByNoField to order by
orderDirectionNoOrder direction
searchKeywordNoSearch keyword for feature name or ID
maintainerNoFilter by maintainer email
archivedNoFilter by archived status

Implementation Reference

  • The handler function that executes the tool logic: validates input using Zod schema, initializes BucketeerClient, prepares the ListFeaturesRequest, calls the API, logs results, and returns structured content or error response.
    handler: async (input: unknown) => {
    	try {
    		// Validate input
    		const params = listFlagsSchema.parse(input);
    
    		logger.debug("Listing feature flags", params);
    
    		// Create API client
    		const client = new BucketeerClient(
    			config.bucketeerHost,
    			config.bucketeerApiKey,
    		);
    
    		// Prepare request
    		const request: ListFeaturesRequest = {
    			environmentId: getEnvironmentId(params.environmentId),
    			pageSize: params.pageSize,
    			cursor: params.cursor,
    			tags: params.tags,
    			orderBy: params.orderBy,
    			orderDirection: params.orderDirection,
    			searchKeyword: params.searchKeyword,
    			maintainer: params.maintainer,
    			archived: params.archived,
    		};
    
    		// Make API call
    		const response = await client.listFeatures(request);
    
    		logger.info(
    			`Successfully listed ${response.features.length} feature flags`,
    		);
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							success: true,
    							features: response.features,
    							cursor: response.cursor,
    							totalCount: response.totalCount,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	} catch (error) {
    		logger.error("Failed to list feature flags", error);
    
    		if (error instanceof z.ZodError) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: JSON.stringify(
    							{
    								success: false,
    								error: "Invalid input parameters",
    								details: error.issues,
    							},
    							null,
    							2,
    						),
    					},
    				],
    				isError: true,
    			};
    		}
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							success: false,
    							error: error instanceof Error ? error.message : "Unknown error",
    						},
    						null,
    						2,
    					),
    				},
    			],
    			isError: true,
    		};
    	}
    },
  • Zod input schema used for validating the parameters in the handler.
    // Input schema for the list-flags tool
    export const listFlagsSchema = z.object({
    	environmentId: z.string().optional(),
    	pageSize: z.number().min(1).max(100).optional().default(20),
    	cursor: z.string().optional(),
    	tags: z.array(z.string()).optional(),
    	orderBy: z.enum(["CREATED_AT", "UPDATED_AT", "NAME"]).optional(),
    	orderDirection: z.enum(["ASC", "DESC"]).optional(),
    	searchKeyword: z.string().optional(),
    	maintainer: z.string().optional(),
    	archived: z.boolean().optional(),
    });
  • Registration of the listFeatureFlags tool (as listFlagsTool) in the central tools array exported from the tools index.
    export const tools = [
    	listFlagsTool,
    	createFlagTool,
    	getFlagTool,
    	updateFlagTool,
    	archiveFlagTool,
    ];
  • Tool object definition including the name 'listFeatureFlags', description, and reference to inputSchema and handler.
    export const listFlagsTool = {
    	name: "listFeatureFlags",
    	description: "List all feature flags in the specified environment",
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions listing 'all' feature flags but doesn't clarify pagination behavior (implied by cursor/pageSize parameters), rate limits, authentication requirements, or what 'all' means in context of filters. The description is minimal and lacks important operational context.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a list operation and front-loads the essential information.

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

Completeness2/5

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

For a tool with 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the relationship between parameters (e.g., how pagination works with filters), what the output looks like, or important behavioral aspects. The high parameter count and lack of structured metadata require more descriptive context.

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 100%, so the schema already documents all 9 parameters thoroughly. The description adds no additional parameter semantics beyond implying environment filtering. This meets the baseline of 3 when schema coverage is high, but doesn't provide extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('feature flags') with scope ('in the specified environment'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getFeatureFlag' which retrieves a single flag, leaving some ambiguity about when to use each.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'getFeatureFlag' for single flag retrieval or 'searchKeyword' parameter for filtered searches. It mentions 'specified environment' but doesn't explain environment selection or prerequisites.

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/bucketeer-io/bucketeer-mcp'

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