# LaunchDarkly A feature management platform that helps teams build better software faster using feature flags. - **Category:** developer tools - **Auth:** API_KEY - **Composio Managed App Available?** N/A - **Tools:** 248 - **Triggers:** 0 - **Slug:** `LAUNCH_DARKLY` - **Version:** 20260312_00 ## Tools ### Add Member to Teams **Slug:** `LAUNCH_DARKLY_ADD_MEMBER_TO_TEAMS` Tool to add a LaunchDarkly member to one or more teams. Use when you need to grant a member access to specific teams within your organization. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique member ID. This is the member's identifier in LaunchDarkly. | | `teamKeys` | array | Yes | List of team keys to add the member to. Each team key must be a valid, existing team in your LaunchDarkly organization. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Apply Approval Request **Slug:** `LAUNCH_DARKLY_APPLY_APPROVAL_REQUEST` Tool to apply an approved approval request in LaunchDarkly. Use when you need to execute changes that have been approved. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The approval request ID to apply. Example: '697ca5410a055f0a0a8079d6' | | `comment` | string | No | Optional comment about the approval request application. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Apply Approval Request for Flag **Slug:** `LAUNCH_DARKLY_APPLY_APPROVAL_REQUEST_FOR_FLAG` Tool to apply an approved approval request for a feature flag in LaunchDarkly. Use when you need to execute changes that have been approved for a specific flag in an environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the approval request to apply. This ID is returned when creating an approval request or can be found using the approval requests API. | | `comment` | string | No | Optional comment about the approval request application. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the approval request is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the approval request to apply. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Copy Feature Flag **Slug:** `LAUNCH_DARKLY_COPY_FEATURE_FLAG` Tool to copy a feature flag's configuration from one environment to another within the same project. Use when you need to replicate flag settings across environments, such as promoting configurations from test to production. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `source` | object | Yes | The source environment from which to copy the feature flag configuration. | | `target` | object | Yes | The target environment to which to copy the feature flag configuration. | | `comment` | string | No | Optional comment describing the purpose of this copy operation. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `excludedActions` | array | No | Optional list of flag changes NOT to copy from source to target. You may include either includedActions or excludedActions, but not both. If neither is provided, all flag changes will be copied. | | `includedActions` | array | No | Optional list of flag changes to copy from source to target. You may include either includedActions or excludedActions, but not both. If neither is provided, all flag changes will be copied. | | `feature_flag_key` | string | Yes | The feature flag key. The key identifies the flag in your code. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Announcement **Slug:** `LAUNCH_DARKLY_CREATE_ANNOUNCEMENT_PUBLIC` Tool to create a public announcement in LaunchDarkly. Use when you need to notify users about system maintenance, important updates, or critical information. Announcements can be scheduled to appear at specific times and optionally set to auto-expire. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `title` | string | Yes | The title of the announcement. This will be displayed as the heading of the announcement. | | `endTime` | integer | No | The end time of the announcement. This is a Unix timestamp in milliseconds. The announcement will automatically hide after this time. If not provided, the announcement will remain visible until manually removed. | | `message` | string | Yes | The message content of the announcement. Supports markdown formatting for rich text display. | | `severity` | string ("info" | "warning" | "critical") | Yes | The severity level of the announcement. This affects how the announcement is displayed to users. | | `startTime` | integer | Yes | The start time of the announcement. This is a Unix timestamp in milliseconds. The announcement will be visible starting from this time. | | `isDismissible` | boolean | Yes | Whether users can dismiss the announcement. If true, users can close the announcement; if false, it will be shown until it expires. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Approval Request **Slug:** `LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST` Tool to create an approval request in LaunchDarkly. Use when you need to request approval for flag changes before they are applied. The request requires a resource ID, description, and a list of instructions in semantic patch format. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment providing additional context about the approval request. | | `resourceId` | string | Yes | String representation of the resource specifier. Format: proj/{projectKey}:env/*:flag/{flagKey}. Note: The environment portion must use wildcard '*' for all environments. Example: 'proj/default:env/*:flag/sample-feature' | | `description` | string | Yes | A brief description of the changes being requested in this approval request. | | `instructions` | array | Yes | Array of instruction objects in semantic patch format. Each instruction must have a 'kind' property specifying the operation type. Supported kinds: addVariation, removeVariation, updateVariation, updateDefaultVariation. | | `notifyTeamKeys` | array | No | Array of team keys whose members should be notified to review this approval request. | | `notifyMemberIds` | array | No | Array of member IDs to notify for reviewing this approval request. These members will receive notifications to review the request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Approval Request for Flag **Slug:** `LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_FOR_FLAG` Tool to create an approval request for a feature flag in LaunchDarkly. Use when you need to request approval for changes to a feature flag before applying them. Approval requests enable workflow controls and review processes for flag changes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the approval request in more detail. | | `description` | string | Yes | A brief description of the changes you're requesting. This helps reviewers understand what the approval request is for. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `instructions` | array | Yes | An array of instruction objects defining the changes to be made to the flag. Each instruction must have a 'kind' field. Common kinds include: 'turnFlagOn', 'turnFlagOff', 'updateFallthrough', 'updateTargets', etc. Example: [{'kind': 'turnFlagOn'}] | | `execution_date` | integer | No | Unix timestamp (in milliseconds) for when the approval should be executed. If not provided, the approval will be executed immediately upon approval. | | `environment_key` | string | Yes | The environment key where the approval request will be created (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `operating_on_id` | string | No | The ID of a scheduled change. Include this if your instructions include editing or deleting a scheduled change. | | `feature_flag_key` | string | Yes | The unique key of the feature flag for which to create an approval request. | | `notify_team_keys` | array | No | An array of team keys. The members of these teams are notified to review the approval request. | | `notify_member_ids` | array | No | An array of member IDs. These members are notified to review the approval request. | | `integration_config` | object | No | Optional integration configuration object for external approval systems. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Approval Request Review **Slug:** `LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_REVIEW` Tool to review an approval request by approving, declining, or commenting on changes. Use when you need to provide feedback or make a decision on a pending approval request in LaunchDarkly. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The approval request ID to review. Example: '6990dd06e218990a1077bc26' | | `kind` | string ("approve" | "comment" | "decline") | Yes | The type of review for this approval request. Use 'approve' to approve the changes, 'decline' to reject them, or 'comment' to add feedback without approving or declining. | | `comment` | string | No | Optional comment about the approval request. Provide context, reasoning, or feedback for your review decision. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Approval Request Review for Flag **Slug:** `LAUNCH_DARKLY_CREATE_APPROVAL_REQUEST_REVIEW_FOR_FLAG` Tool to review an approval request for a feature flag by approving, declining, or commenting on the changes. Use when you need to provide feedback or make a decision on a pending flag approval request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier of the approval request to review. | | `kind` | string ("approve" | "comment" | "decline") | Yes | The type of review for this approval request: 'approve' to approve changes, 'decline' to reject changes, or 'comment' to add comments without approval decision. | | `comment` | string | No | Optional comment about the approval request review. | | `project_key` | string | Yes | The project key identifying the project containing the feature flag. | | `environment_key` | string | Yes | The environment key where the approval request is configured (e.g., 'test', 'production'). | | `feature_flag_key` | string | Yes | The feature flag key identifying the specific flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Big Segment Export **Slug:** `LAUNCH_DARKLY_CREATE_BIG_SEGMENT_EXPORT` Tool to create an export for a big segment in LaunchDarkly. Use when you need to export a synced segment or list-based segment with 15,000+ entries. The export ID is returned and can be used to check export status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the segment. Use 'List Projects' action to find available project keys. | | `segment_key` | string | Yes | The segment key identifying the specific big segment to export. Big segments are synced segments or list-based segments with 15,000+ entries. | | `environment_key` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Big Segment Store Integration **Slug:** `LAUNCH_DARKLY_CREATE_BIG_SEGMENT_STORE_INTEGRATION` Tool to create a persistent store integration for big segments in LaunchDarkly. Use when you need to set up a new Redis or DynamoDB integration for syncing large list-based segments. This integration is required for server-side SDKs to evaluate segments synced from external tools. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `on` | boolean | No | Whether the integration configuration is active. Default value is false if not specified. | | `name` | string | No | Human-readable name to identify the integration. If not provided, a default name will be assigned. | | `tags` | array | No | List of tags to associate with the integration for organization and filtering. | | `config` | object | Yes | Configuration settings for the integration. For Redis: required field is 'host' (string), optional fields are 'port' (string, e.g., '6379'), 'username' (string), 'password' (string), 'tlsEnabled' (bool). For DynamoDB: required fields vary based on AWS setup (table name, region, role ARN, etc.). | | `project_key` | string | Yes | The project key identifying the project for the integration. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the integration will be configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `integration_key` | string ("redis" | "dynamodb") | Yes | The type of big segment store integration to create, either 'redis' or 'dynamodb'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Custom Role **Slug:** `LAUNCH_DARKLY_CREATE_CUSTOM_ROLE` Tool to create a new custom role in LaunchDarkly. Use when you need to define a custom set of permissions for members or teams. The role must have a unique key and at least one policy statement defining the allowed or denied actions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The custom role key. Must be unique within the account. | | `name` | string | Yes | A human-friendly name for the custom role. | | `policy` | array | Yes | An array of policy statements that define the permissions for this custom role. Each statement must have an 'effect' and can specify 'resources', 'actions', 'notResources', or 'notActions'. | | `description` | string | No | Description of the custom role. | | `basePermissions` | string | No | Legacy base permissions for the role. This field is deprecated and should not be used for new roles. | | `resourceCategory` | string ("organization" | "project" | "any") | No | Category of resources this role applies to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Data Export Destination **Slug:** `LAUNCH_DARKLY_CREATE_DESTINATION` Tool to create a new Data Export destination for exporting LaunchDarkly event data to external services. Use when you need to set up integrations with services like Kinesis, Google PubSub, Azure Event Hubs, or other supported destinations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `on` | boolean | No | Whether the export should be enabled immediately after creation. Displayed as the integration status in the LaunchDarkly UI. Defaults to false if not specified. | | `kind` | string ("google-pubsub" | "kinesis" | "mparticle" | "segment" | "azure-event-hubs" | "snowflake-v2" | "databricks" | "bigquery" | "redshift") | Yes | The type of Data Export destination. Each destination type requires specific configuration parameters in the 'config' field. | | `name` | string | Yes | A human-readable name for your Data Export destination. | | `config` | object | Yes | Configuration parameters required for the destination type. For Kinesis: requires 'region', 'roleArn', 'streamName'. For Google PubSub: requires 'project', 'topic'. For Azure Event Hubs: requires 'namespace', 'name', 'policyName', 'policyKey'. Configuration varies by destination kind. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the destination should be created (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Environment **Slug:** `LAUNCH_DARKLY_CREATE_ENVIRONMENT` Tool to create a new environment within a LaunchDarkly project. Use when you need to add a new environment such as development, staging, or production. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A project-unique key for the new environment. Must be unique within the project. | | `name` | string | Yes | A human-friendly name for the new environment. | | `tags` | array | No | Tags to apply to the new environment. | | `color` | string | Yes | A color to indicate this environment in the UI. Provide as a hex color code without the # symbol. | | `source` | object | No | Source environment configuration for cloning. | | `critical` | boolean | No | Whether the environment is critical (e.g., production environments). | | `defaultTtl` | integer | No | The default time (in minutes) that the PHP SDK can cache feature flag rules locally. | | `projectKey` | string | Yes | The project key identifying the project where the environment will be created. Use LIST_PROJECTS to discover available project keys. | | `secureMode` | boolean | No | Ensures that one end user of the client-side SDK cannot inspect the variations for another end user. | | `confirmChanges` | boolean | No | Requires confirmation for all flag and segment changes via the UI in this environment. | | `requireComments` | boolean | No | Requires comments for all flag and segment changes via the UI in this environment. | | `defaultTrackEvents` | boolean | No | Enables tracking detailed information for new flags by default. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Experiment **Slug:** `LAUNCH_DARKLY_CREATE_EXPERIMENT` Tool to create a new experiment in LaunchDarkly. Use when you need to set up A/B tests or multivariate experiments to measure the impact of feature flag variations on specified metrics. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The unique key for the experiment. This key is used to reference the experiment in API calls and must be unique within the project and environment. | | `name` | string | Yes | The human-readable name of the experiment. | | `tags` | array | No | Tags for the experiment to help with organization and filtering. | | `holdoutId` | string | No | The ID of the holdout to associate with this experiment. | | `iteration` | object | Yes | The initial iteration configuration for the experiment. This defines the hypothesis, metrics, treatments, and flags for the experiment. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys. | | `description` | string | No | A detailed description of the experiment. | | `maintainerId` | string | No | The ID of the member who maintains this experiment. If not provided, the creator will be set as the maintainer. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Extinction Events **Slug:** `LAUNCH_DARKLY_CREATE_EXTINCTION` Tool to create new extinction events for feature flags in LaunchDarkly. Use when you need to record that a feature flag has been removed from the codebase. Extinction events track when flags are no longer referenced in code. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name. This is the name of the code reference repository configured in LaunchDarkly. | | `branch` | string | Yes | The URL-encoded branch name. | | `extinctions` | array | Yes | Array of extinction event objects to create. Each object represents a flag that has been removed from the codebase. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Feature Flag **Slug:** `LAUNCH_DARKLY_CREATE_FEATURE_FLAG` Tool to create a new feature flag in LaunchDarkly. Use when you need to create a feature flag with a name, key, and optional variations. Supports creating both standard and migration flags. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key used to reference the flag in your code. Must be unique within the project. | | `name` | string | Yes | A human-friendly name for the feature flag. | | `tags` | array | No | Tags for the feature flag. Defaults to an empty array. | | `clone` | string | No | The key of the feature flag to be cloned. Setting this copies the full targeting configuration for all environments from the original flag to the new flag. | | `purpose` | string ("migration" | "holdout") | No | Purpose of the feature flag. | | `defaults` | object | No | Default variation settings for a feature flag. | | `isFlagOn` | boolean | No | Whether to automatically turn the flag on across all environments at creation. Defaults to false. | | `temporary` | boolean | No | Whether the flag is a temporary flag. Defaults to true. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project where the flag will be created. Use 'List Projects' action to find available project keys. | | `variations` | array | No | An array of possible variations for the flag. If omitted, two boolean variations of true and false will be used. | | `description` | string | No | Description of the feature flag. Defaults to an empty string. | | `maintainerId` | string | No | The ID of the member who maintains this feature flag. | | `customProperties` | object | No | Custom properties for the feature flag. | | `maintainerTeamKey` | string | No | The key of the team that maintains this feature flag. | | `migrationSettings` | object | No | Migration settings for a feature flag. | | `initialPrerequisites` | array | No | Initial set of prerequisite flags for all environments. | | `clientSideAvailability` | object | No | Client-side availability settings for a feature flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Flag Scheduled Changes **Slug:** `LAUNCH_DARKLY_CREATE_FLAG_CONFIG_SCHEDULED_CHANGES` Tool to create a scheduled changes workflow for a feature flag in LaunchDarkly. Scheduled changes allow you to plan flag configuration updates for a future time. Use when you need to automate flag changes at a specific date/time. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the purpose of these scheduled changes. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `instructions` | array | Yes | List of instructions to execute at the scheduled time. Each instruction must have a 'kind' field (e.g., 'turnFlagOn', 'turnFlagOff'). | | `execution_date` | integer | Yes | Unix timestamp in milliseconds indicating when the scheduled changes should be executed. | | `environment_key` | string | Yes | The environment key where the scheduled changes will be applied (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag to schedule changes for. | | `ignore_conflicts` | boolean | No | Whether to succeed (true) or fail (false) when these instructions conflict with existing scheduled changes. If not specified, conflicts will cause the request to fail. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Flag Copy Config Approval Request **Slug:** `LAUNCH_DARKLY_CREATE_FLAG_COPY_CONFIG_APPROVAL_REQUEST` Tool to create an approval request for copying a feature flag's configuration from one environment to another. Use when you need to promote flag settings across environments with approval workflow. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `source` | object | Yes | The source environment from which to copy the flag configuration. | | `comment` | string | No | Optional comment providing additional context about the approval request. | | `description` | string | Yes | A brief description of the changes and reason for copying the flag configuration. This helps reviewers understand the purpose of the approval request. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key for the target environment where the flag configuration will be copied to (e.g., 'production'). Use 'Get Environments' action to list available environments. | | `excluded_actions` | array | No | Optional list of flag changes NOT to copy from the source environment to the target environment. You may include either 'included_actions' or 'excluded_actions', but not both. If neither are included, all flag changes will be copied. | | `feature_flag_key` | string | Yes | The unique key of the feature flag whose configuration will be copied. | | `included_actions` | array | No | Optional list of specific flag changes to copy from the source environment to the target environment. You may include either 'included_actions' or 'excluded_actions', but not both. If neither are included, all flag changes will be copied. | | `notify_team_keys` | array | No | An array of team keys whose members will be notified to review the approval request. | | `notify_member_ids` | array | No | An array of member IDs to notify for reviewing the approval request. These members will receive notifications to review and approve/decline the request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Flag Import Configuration **Slug:** `LAUNCH_DARKLY_CREATE_FLAG_IMPORT_CONFIGURATION` Tool to create a new flag import configuration for importing feature flags from external feature management systems like Split or Unleash. Use when setting up automated flag synchronization from another platform into LaunchDarkly. The config object structure varies by integration key. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Human-readable name to identify the flag import configuration. | | `tags` | array | No | List of tags to associate with the flag import configuration for organization and filtering. | | `config` | object | Yes | Configuration object containing integration-specific settings. The structure varies based on the integration_key. For 'split': requires 'workspaceId', 'workspaceApiKey', 'environmentId', 'ldApiKey', 'ldMaintainer', 'ldTag', and optional 'splitTag'. For 'unleash': check the integration's formVariables in manifest.json. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integration_key` | string ("split" | "unleash") | Yes | The integration key identifying the feature management system from which the import occurs. Choose 'SPLIT' for Split.io or 'UNLEASH' for Unleash. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Flag Link **Slug:** `LAUNCH_DARKLY_CREATE_FLAG_LINK` Tool to create a new flag link in LaunchDarkly. Flag links connect feature flags to external resources such as documentation, issue trackers (like JIRA), or code repositories. Use when you need to associate a flag with an external URL for tracking or documentation purposes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key identifier for the flag link. This field is required and cannot be empty. | | `title` | string | No | The title of the flag link. This is displayed as the link name in LaunchDarkly. | | `deepLink` | string | Yes | The URL for the external resource you are linking the flag to. This is the actual URL that the link points to. | | `metadata` | object | No | The metadata required by this integration in order to create a flag link, if this is a flag link for an existing integration. Defined in the integration's manifest.json file under flagLink. | | `timestamp` | integer | No | Unix timestamp in milliseconds. If not provided, the current time will be used. | | `description` | string | No | The description of the flag link. Provides additional context about what the link represents. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integrationKey` | string | No | The integration key for an integration whose manifest.json includes the flagLink capability, if this is a flag link for an existing integration. Do not include for URL flag links. | | `feature_flag_key` | string | Yes | The unique key of the feature flag to link to an external resource. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Holdout **Slug:** `LAUNCH_DARKLY_CREATE_HOLDOUT` Tool to create a new holdout in LaunchDarkly for experiment control groups. Use when you need to create a holdout to measure the impact of features against a control group. Requires LD-API-Version: beta header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key that identifies the holdout. This key must be unique within the project and environment. | | `name` | string | Yes | A human-friendly name for the holdout. This will be displayed in the LaunchDarkly UI. | | `metrics` | array | No | Details on the metrics for this holdout. If not specified, only the primary metric will be included. Each metric must have a 'key' field. | | `attributes` | array | No | The attributes that the holdout iteration's results can be sliced by. These should be context attributes that exist in your LaunchDarkly environment. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `description` | string | No | An optional description of the holdout. Provides additional context about the holdout's purpose. | | `maintainerId` | string | Yes | The ID of the member who will maintain this holdout. Use GET_MEMBERS to find valid member IDs. | | `holdoutAmount` | string | No | Audience allocation for the holdout as a percentage string. For example, '10' means 10% of traffic is allocated to the holdout. If not specified, defaults to a value set by LaunchDarkly. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `primaryMetricKey` | string | Yes | The key of the primary metric for this holdout. This metric must already exist in the project. Use LIST_METRICS to discover available metrics. | | `randomizationUnit` | string | Yes | The chosen randomization unit for the holdout base experiment. This determines how traffic is allocated. Common values: 'user', 'device', 'session'. | | `prerequisiteFlagKey` | string | Yes | The key of the flag that the holdout is dependent on. This flag must already exist and have purpose 'holdout'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Integration Configuration **Slug:** `LAUNCH_DARKLY_CREATE_INTEGRATION_CONFIGURATION` Tool to create a new integration configuration in LaunchDarkly. Use when you need to set up automated workflows with external services like Slack, Datadog, Jira, custom webhooks, or other third-party integrations. Note: This endpoint requires the 'LD-API-Version: beta' header which is automatically included. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of the integration configuration. This is a human-readable label to identify the configuration. | | `tags` | array | No | Tags for the integration configuration. Use tags to organize and categorize integrations. | | `enabled` | boolean | No | Whether the integration configuration should be enabled. If omitted, defaults to true. | | `configValues` | object | Yes | The unique set of fields required to configure the integration. The required fields vary by integration type. Refer to the 'formVariables' field in the corresponding manifest.json at https://github.com/launchdarkly/integration-framework/tree/main/integrations for the specific fields needed for your integration. | | `integration_key` | string | Yes | The integration key identifying the type of integration. Common values include 'slack', 'datadog', 'jira', 'custom-approvals', 'webhook', etc. This must match an available integration in LaunchDarkly's integration framework. | | `capabilityConfig` | object | No | Configuration for integration capabilities. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Experiment Iteration **Slug:** `LAUNCH_DARKLY_CREATE_ITERATION` Tool to create a new iteration for an experiment in LaunchDarkly. Use when you need to set up a new experiment iteration with specific hypothesis, metrics, treatments (variations), and feature flag configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flags` | object | Yes | Dictionary mapping flag keys to their configuration for this experiment. Keys are flag keys, values are flag configuration objects. | | `metrics` | array | Yes | List of metrics to track in this iteration. At least one metric must be specified, and one should be marked as primary. | | `attributes` | array | No | The attributes that this iteration's results can be sliced by for analysis. | | `hypothesis` | string | Yes | The hypothesis for this experiment iteration - the expected outcome you're testing. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project containing the experiment. Use LIST_PROJECTS to discover available project keys. | | `treatments` | array | Yes | List of treatment groups for the experiment. Must include at least 2 treatments, and exactly one must be marked as baseline. | | `experimentKey` | string | Yes | The unique key identifying the experiment to add this iteration to. Use GET_EXPERIMENTS to discover available experiment keys. | | `environmentKey` | string | Yes | The environment key where the experiment iteration will be created. Common values include 'production', 'staging', 'test'. | | `primaryFunnelKey` | string | No | The key of the primary funnel (metric group) for this experiment. Either this or primarySingleMetricKey must be specified. | | `randomizationUnit` | string | No | The unit of randomization for this iteration. Defaults to 'user'. | | `canReshuffleTraffic` | boolean | No | Whether to allow the experiment to reassign traffic to different variations when you increase or decrease the traffic in your experiment audience (true) or keep all traffic assigned to its initial variation (false). Defaults to true. | | `primarySingleMetricKey` | string | No | The key of the primary single metric for this experiment. Either this or primaryFunnelKey must be specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Layer **Slug:** `LAUNCH_DARKLY_CREATE_LAYER` Tool to create a new layer in a LaunchDarkly project. Use when you need to set up a new layer for organizing experiments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | Unique identifier for the layer. Must be unique within the project. | | `name` | string | Yes | Human-readable name for the layer. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project where the layer will be created. Use LIST_PROJECTS to discover available project keys. | | `description` | string | Yes | Description explaining the purpose and usage of the layer. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Members **Slug:** `LAUNCH_DARKLY_CREATE_MEMBERS` Tool to invite one or more new members to join a LaunchDarkly account. Use when you need to add new team members. Each member receives an invitation email and must have an email address and either a role or customRoles. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `members` | array | Yes | Array of new members to invite. Each member must have an email and either a role or customRoles. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Metric **Slug:** `LAUNCH_DARKLY_CREATE_METRIC` Tool to create a new metric in LaunchDarkly. Use when you need to define a new metric for tracking pageviews, clicks, or custom events in experiments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key to reference the metric | | `kind` | string ("pageview" | "click" | "custom") | Yes | The kind of event your metric will track | | `name` | string | No | A human-friendly name for the metric | | `tags` | array | No | Tags for the metric | | `unit` | string | No | The unit of measure. Applicable for numeric custom metrics only. | | `urls` | array | No | One or more target URLs. Required for click and pageview metrics only. | | `filters` | object | No | Filter configuration for the metric. | | `eventKey` | string | No | The event key to use in your code. Required for custom conversion/binary and custom numeric metrics only. | | `selector` | string | No | One or more CSS selectors. Required for click metrics only. | | `isNumeric` | boolean | No | Whether to track numeric changes in value against a baseline (true) or to track a conversion when an end user takes an action (false). Required for custom metrics only. | | `dataSource` | object | No | Data source configuration for a metric. | | `projectKey` | string | Yes | The project key identifying the project where the metric will be created. Use LIST_PROJECTS to discover available project keys. | | `description` | string | No | Description of the metric | | `analysisType` | string ("mean" | "percentile") | No | The method for analyzing metric events. | | `eventDefault` | object | No | Default event configuration. | | `maintainerId` | string | No | The ID of the member who maintains this metric | | `percentileValue` | integer | No | The percentile for the analysis method. An integer denoting the target percentile between 0 and 100. Required when analysisType is percentile. | | `successCriteria` | string ("HigherThanBaseline" | "LowerThanBaseline") | No | Success criteria for custom metrics. | | `randomizationUnits` | array | No | An array of randomization units allowed for this metric | | `unitAggregationType` | string ("average" | "sum") | No | The method by which multiple unit event values are aggregated. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Metric Group **Slug:** `LAUNCH_DARKLY_CREATE_METRIC_GROUP` Tool to create a new metric group in LaunchDarkly. Use when you need to organize multiple metrics together for experiments or analysis. Metric groups must contain at least 2 metrics. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key to reference the metric group | | `kind` | string ("funnel" | "standard" | "guardrail") | Yes | The type of the metric group | | `name` | string | Yes | A human-friendly name for the metric group | | `tags` | array | Yes | Tags for the metric group | | `metrics` | array | Yes | An ordered list of the metrics in this metric group. Must contain at least 2 metrics. | | `projectKey` | string | Yes | The project key identifying the project where the metric group will be created. Use LIST_PROJECTS to discover available project keys. | | `description` | string | No | Description of the metric group | | `maintainerId` | string | Yes | The ID of the member who maintains this metric group. Use GET_MEMBERS to find available member IDs. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Migration Safety Issues **Slug:** `LAUNCH_DARKLY_CREATE_MIGRATION_SAFETY_ISSUES` Tool to check migration safety issues for a feature flag patch. Returns safety issues associated with the provided semantic patch instructions. Use when you need to validate if flag changes will cause migration issues before applying them. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment providing additional context for the patch. Useful for documentation and audit trails. | | `flagKey` | string | Yes | The migration flag key identifying the specific flag to check for safety issues. | | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of semantic patch instructions for the flag. Each instruction must have a 'kind' field specifying the operation type. These are the same instructions that are valid for feature flags. Common kinds include 'turnFlagOn', 'turnFlagOff', 'addRule', 'removeRule', 'updateFallthroughVariationOrRollout', etc. | | `environmentKey` | string | Yes | The environment key where the migration safety check will be performed (e.g., 'production', 'staging'). Use GET_ENVIRONMENTS to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create OAuth 2.0 Client **Slug:** `LAUNCH_DARKLY_CREATE_O_AUTH2_CLIENT` Tool to create (register) a LaunchDarkly OAuth 2.0 client. Use when you need to build custom integrations using LaunchDarkly as your identity provider. The client secret is only returned upon creation, so save it securely. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of your new LaunchDarkly OAuth 2.0 client. | | `description` | string | No | Description of your OAuth 2.0 client. | | `redirectUri` | string | Yes | The redirect URI for your new OAuth 2.0 application. This should be an absolute URL conforming with the standard HTTPS protocol. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Project **Slug:** `LAUNCH_DARKLY_CREATE_PROJECT` Tool to create a new project with the given key and name. Project keys must be unique within an account. Use when you need to set up a new project in LaunchDarkly. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key used to reference the project in your code. Project keys must be unique within an account. | | `name` | string | Yes | A human-friendly name for the project. | | `tags` | array | No | Tags for the project. | | `environments` | array | No | Creates the provided environments for this project. If omitted default environments will be created instead. | | `namingConvention` | object | No | Naming convention settings for flag keys in the project. | | `includeInSnippetByDefault` | boolean | No | Whether or not flags created in this project are made available to the client-side JavaScript SDK by default. | | `defaultClientSideAvailability` | object | No | Client-side SDK availability settings for the project. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Relay Proxy Auto Configuration **Slug:** `LAUNCH_DARKLY_CREATE_RELAY_AUTO_CONFIG` Tool to create a new Relay Proxy configuration in LaunchDarkly. Use when you need to set up a new Relay Proxy with specific access policies for environments and projects. The response includes the full configuration key which is only shown once. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | A human-friendly name for the Relay Proxy configuration. This will help identify the configuration in the LaunchDarkly UI. | | `policy` | array | Yes | An array of policy statements that define what environments and projects the Relay Proxy should include or exclude. Each statement must have an 'effect' field and optionally 'resources' and 'actions' fields. To learn more, read the LaunchDarkly documentation on inline policies. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Release for Flag **Slug:** `LAUNCH_DARKLY_CREATE_RELEASE_FOR_FLAG` Tool to create a release by adding a flag to a release pipeline in LaunchDarkly. Use when you need to add a feature flag to a release pipeline for progressive rollout across multiple phases. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flag_key` | string | Yes | The unique key of the feature flag to add to the release pipeline. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag. Use 'List Projects' action to find available project keys. | | `releasePipelineKey` | string | Yes | The key of the release pipeline to attach the flag to. Use 'Get All Release Pipelines' action to find available pipeline keys. | | `releaseVariationId` | string | No | The variation ID to release across all phases. If not specified, the default variation will be used. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Release Pipeline **Slug:** `LAUNCH_DARKLY_CREATE_RELEASE_PIPELINE` Tool to create a release pipeline in LaunchDarkly. Release pipelines standardize and automate the feature flag release process across a series of phases. Use when you need to set up a structured rollout process. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique identifier for the release pipeline. This must be unique within the project. | | `name` | string | Yes | A human-friendly name for the release pipeline. | | `tags` | array | No | Tags for organizing and categorizing the release pipeline. | | `phases` | array | Yes | An ordered list of release pipeline phases. Each phase is a logical grouping of one or more environments that share attributes for rolling out changes. | | `isLegacy` | boolean | No | Whether the pipeline is enabled for Release Automation. | | `description` | string | No | A description of the release pipeline. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `isProjectDefault` | boolean | No | Whether this pipeline should be set as the default pipeline for the project. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Release Policy **Slug:** `LAUNCH_DARKLY_CREATE_RELEASE_POLICY` Tool to create a new release policy for a specified project. Use when you need to set up release automation policies for progressive or guarded rollouts. Requires beta API version header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key used to reference the release policy. Must be unique within the project. | | `name` | string | Yes | A human-friendly name for the release policy. | | `scope` | object | No | Target environments and flag tags for a release policy. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | | `releaseMethod` | string ("guarded-release" | "progressive-release") | Yes | The release method for this policy: 'guarded-release' monitors metrics during rollout, 'progressive-release' follows staged rollout without metric monitoring. | | `guardedReleaseConfig` | object | No | Configuration for guarded release policies. | | `progressiveReleaseConfig` | object | No | Configuration for progressive release policies. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Repository **Slug:** `LAUNCH_DARKLY_CREATE_REPOSITORY` Tool to create a code reference repository with the specified name. Use when you need to set up a new repository for code reference scanning in LaunchDarkly. This enables tracking of feature flag usage across your codebase. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The repository name. | | `type` | string ("bitbucket" | "custom" | "github" | "gitlab") | No | Enum for supported repository types. | | `sourceLink` | string | No | A URL to access the repository. | | `defaultBranch` | string | No | The repository's default branch. If not specified, the default value is 'main'. | | `hunkUrlTemplate` | string | No | A template for constructing a valid URL to view the hunk. | | `commitUrlTemplate` | string | No | A template for constructing a valid URL to view the commit. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Segment **Slug:** `LAUNCH_DARKLY_CREATE_SEGMENT` Tool to create a new segment in LaunchDarkly. Segments are groups of contexts that you can use to manage flag targeting rules. Use when you need to organize users, devices, or other contexts into logical groups for feature flag targeting. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key used to reference the segment. Must be unique within the project and environment. Use lowercase letters, numbers, dots, hyphens, and underscores. | | `name` | string | Yes | A human-friendly name for the segment. This is displayed in the LaunchDarkly UI. | | `tags` | array | No | Tags for organizing and filtering segments. Use tags to categorize segments for easier management. | | `unbounded` | boolean | No | Whether to create a standard segment (false) or a big segment (true). Standard segments include rule-based and smaller list-based segments. Big segments include larger list-based segments and synced segments. Only use a big segment if you need to add more than 15,000 individual targets. | | `description` | string | No | A description of the segment's purpose. Helps document why the segment exists and how it should be used. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the segment will be created (e.g., 'production', 'staging'). Use 'Get Environments' action to list available environments. | | `unboundedContextKind` | string | No | For big segments, the targeted context kind (e.g., 'user', 'device'). Required when unbounded is true. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Audit Log Subscription **Slug:** `LAUNCH_DARKLY_CREATE_SUBSCRIPTION` Tool to create a new audit log subscription for forwarding LaunchDarkly audit events to external services. Use when you need to set up integrations with monitoring or logging platforms like Datadog, Splunk, Elastic, or Microsoft Teams to receive real-time audit log notifications. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `on` | boolean | No | Whether you want your subscription to actively send events immediately after creation. If true, the subscription will begin forwarding audit log events to the configured destination. If false or omitted, the subscription will be created but will not send events until enabled. | | `url` | string | No | Slack webhook receiver URL. This field is only necessary for legacy Slack webhook integrations and should not be used for other integration types. | | `name` | string | Yes | A human-friendly name for your audit log subscription. This name helps identify the subscription in the LaunchDarkly UI and API responses. | | `tags` | array | No | An array of tags for organizing and filtering this subscription. Tags can be used for categorization, filtering, and management of multiple subscriptions. | | `apiKey` | string | No | Datadog API key. This field is only necessary for legacy Datadog webhook integrations and should not be used for other integration types. For modern integrations, include the API key in the 'config' field instead. | | `config` | object | Yes | The unique set of fields required to configure an audit log subscription integration of this type. Configuration fields vary by integration type. For example, Datadog requires 'apiKey', while other integrations may require different fields like 'url', 'token', or service-specific credentials. Refer to the integration's manifest.json at https://github.com/launchdarkly/integration-framework/tree/main/integrations for a full list of required and optional fields for your chosen integration. | | `statements` | array | No | An array of policy statements defining which audit log events this subscription should receive. Each statement uses a custom role policy format with 'effect', 'resources', and optionally 'actions', 'notResources', and 'notActions'. This allows fine-grained control over which resource types and actions trigger notifications. See https://launchdarkly.com/docs/home/account/role-concepts for more details on custom role policies. | | `integration_key` | string | Yes | The integration key identifying the type of audit log subscription to create (e.g., 'datadog', 'dynatrace', 'elastic', 'honeycomb', 'logdna', 'msteams', 'new-relic-apm', 'signalfx', 'splunk'). This key determines which external service will receive the audit log events. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Team **Slug:** `LAUNCH_DARKLY_CREATE_TEAM` Tool to create a new team in LaunchDarkly. Use when you need to set up a new team for organizing members and managing permissions. To learn more, read Creating a team documentation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The unique key to identify the team. Must be unique within the account. | | `name` | string | Yes | A human-friendly name for the team. | | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Options: 'members' (includes member details), 'roles' (includes custom roles), 'projects' (includes projects with write access), 'maintainers' (includes maintainer list). Example: 'members,maintainers'. | | `memberIDs` | array | No | A list of member IDs who will belong to the team. | | `description` | string | No | A description of the team's purpose and responsibilities. | | `customRoleKeys` | array | No | List of custom role keys that the team will have access to. | | `roleAttributes` | object | No | Custom role attributes assigned to the team. | | `permissionGrants` | array | No | A list of permission grants. Permission grants allow access to a specific action, without having to create or update a custom role. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Flag Trigger Workflow **Slug:** `LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW` Creates a flag trigger workflow in LaunchDarkly. Flag triggers allow you to automatically toggle feature flags on or off in response to external events (e.g., monitoring alerts from Datadog, Honeycomb, or custom webhooks). The trigger generates a unique URL that can be called to execute the configured flag action. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | An optional comment describing the purpose of this trigger for documentation | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project | | `instructions` | array | No | List of flag actions to execute when the trigger fires. Each instruction specifies what action to take (turnFlagOn or turnFlagOff) | | `environment_key` | string | Yes | The environment key where the trigger will be active (e.g., 'production', 'test') | | `integration_key` | string | No | The integration identifier for the trigger. Use 'generic-trigger' for custom webhooks, or specific integration keys like 'datadog', 'honeycomb', 'dynatrace' for supported integrations | | `feature_flag_key` | string | Yes | The unique key identifying the feature flag to attach the trigger to | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Webhook **Slug:** `LAUNCH_DARKLY_CREATE_WEBHOOK` Tool to create a new webhook in LaunchDarkly. Use when you need to set up HTTP callbacks to receive notifications about events in your LaunchDarkly environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `on` | boolean | Yes | Whether this webhook is enabled. Set to true to activate the webhook immediately. | | `url` | string | Yes | The URL of the remote webhook endpoint. LaunchDarkly will send HTTP POST payloads to this URL when events occur. | | `name` | string | No | A human-readable name for your webhook. Helps identify the webhook's purpose in the LaunchDarkly UI. | | `sign` | boolean | Yes | Whether to sign webhook requests with a signature header. If true and no secret is provided, LaunchDarkly will automatically generate a secret. | | `tags` | array | No | List of tags for organizing and categorizing this webhook. | | `secret` | string | No | Secret key for signing webhook requests. Only used if 'sign' is true. If omitted when 'sign' is true, LaunchDarkly generates a secret automatically. | | `statements` | array | No | Custom role policy statements that define which resource kinds and actions trigger this webhook. If omitted, the webhook responds to all events. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Workflow **Slug:** `LAUNCH_DARKLY_CREATE_WORKFLOW` Tool to create a workflow in LaunchDarkly for automating flag changes. Use when you need to schedule flag changes or set up approval-based flag management. Workflows can execute flag actions based on time schedules or approval conditions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Human-readable name for the workflow | | `stages` | array | Yes | List of workflow stages. At least one stage is required. Each stage contains conditions and actions. | | `dry_run` | boolean | No | Whether to call the endpoint in dry-run mode to validate without creating | | `description` | string | No | Detailed description of what the workflow does | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `template_key` | string | No | The template key to apply as a starting point for the new workflow (query parameter) | | `environment_key` | string | Yes | The environment key where the workflow will run (e.g., 'test', 'production') | | `feature_flag_key` | string | Yes | The feature flag key that this workflow will manage | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create Workflow Template **Slug:** `LAUNCH_DARKLY_CREATE_WORKFLOW_TEMPLATE` Tool to create a workflow template in LaunchDarkly. Workflow templates provide reusable patterns for common flag change workflows. Use when you need to standardize workflow processes across teams or projects. Either provide an existing workflowId to convert a workflow into a template, or provide stages with flagKey and environmentKey to define a new template from scratch. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | Unique identifier for the workflow template. Must be unique across all templates in the account. | | `name` | string | No | Human-readable name for the workflow template | | `stages` | array | No | List of workflow stages defining the template. Either workflowId or stages must be provided. When stages is provided, flagKey and environmentKey are also required. | | `flagKey` | string | No | The feature flag key to associate with the template. Required when stages is provided. | | `projectKey` | string | No | The project key to associate with the template | | `workflowId` | string | No | ID of an existing workflow to use as the basis for this template. Either workflowId or stages must be provided. | | `description` | string | No | Detailed description of what the workflow template does and when to use it | | `environmentKey` | string | No | The environment key to associate with the template. Required when stages is provided. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Announcement **Slug:** `LAUNCH_DARKLY_DELETE_ANNOUNCEMENT_PUBLIC` Tool to permanently delete an announcement from LaunchDarkly. Use when you need to remove an announcement that is no longer needed. Once deleted, the announcement cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `announcementId` | string | Yes | The unique identifier of the announcement to delete. This ID is returned when creating an announcement or can be retrieved by listing announcements. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Approval Request **Slug:** `LAUNCH_DARKLY_DELETE_APPROVAL_REQUEST` Tool to delete an approval request in LaunchDarkly. Use when you need to remove a pending or declined approval request. Once deleted, the approval request cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the approval request to delete. This is the approval request ID returned when creating or listing approval requests. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Approval Request for Flag **Slug:** `LAUNCH_DARKLY_DELETE_APPROVAL_REQUEST_FOR_FLAG` Permanently deletes an approval request for a feature flag in LaunchDarkly. Approval requests allow teams to review and approve flag changes before they are applied. Once deleted, the approval request cannot be recovered. Ensure you have the correct approval request ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the approval request to delete. This ID is returned when creating an approval request or can be found using the approval requests API. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the approval request is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the approval request to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Big Segment Store Integration **Slug:** `LAUNCH_DARKLY_DELETE_BIG_SEGMENT_STORE_INTEGRATION` Tool to permanently delete a persistent store integration for big segments. Each integration uses either Redis or DynamoDB. Use when you need to remove a big segment store configuration from an environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the integration. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the big segment store integration to delete. | | `environment_key` | string | Yes | The environment key where the integration is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `integration_key` | string ("redis" | "dynamodb") | Yes | The type of big segment store integration, either 'redis' or 'dynamodb'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Branches from Code Reference Repository **Slug:** `LAUNCH_DARKLY_DELETE_BRANCHES` Asynchronously deletes multiple branches from a LaunchDarkly code reference repository. Use this tool to clean up old or unused branches from your code reference configuration. The operation is asynchronous - branches are queued for deletion rather than deleted immediately. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name to delete branches for. This is the name of the code reference repository configured in LaunchDarkly. | | `branches` | array | Yes | Array of branch names to delete from the repository. Each branch name should be a string. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Custom Role **Slug:** `LAUNCH_DARKLY_DELETE_CUSTOM_ROLE` Permanently deletes a custom role from LaunchDarkly. Once deleted, the role cannot be recovered and will be removed from all members and teams it was assigned to. Ensure you have the correct role key before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `custom_role_key` | string | Yes | The unique key identifying the custom role to delete. This is the key used when the role was created (not the role name or ID). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Data Export Destination **Slug:** `LAUNCH_DARKLY_DELETE_DESTINATION` Permanently deletes a Data Export destination from LaunchDarkly. Data Export destinations allow you to export event data to external services. Once deleted, the destination cannot be recovered. Ensure you have the correct destination ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the Data Export destination to delete. This ID is returned when creating a destination or can be found by listing destinations. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the destination is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Environment **Slug:** `LAUNCH_DARKLY_DELETE_ENVIRONMENT` Tool to permanently delete an environment from a LaunchDarkly project. Once deleted, the environment and its configuration cannot be recovered. Ensure you have the correct project and environment keys before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the environment. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The unique key of the environment to delete (e.g., 'test', 'staging'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Feature Flag **Slug:** `LAUNCH_DARKLY_DELETE_FEATURE_FLAG` Tool to permanently delete a feature flag from LaunchDarkly. Use when you need to remove a feature flag that is no longer needed. Once deleted, the flag cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `feature_flag_key` | string | Yes | The feature flag key identifying the flag to delete. The key identifies the flag in your code. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Flag Scheduled Changes **Slug:** `LAUNCH_DARKLY_DELETE_FLAG_CONFIG_SCHEDULED_CHANGES` Tool to delete scheduled changes workflow for a feature flag in LaunchDarkly. Scheduled changes allow you to plan flag configuration updates for a future time. Once deleted, the scheduled changes cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the scheduled change to delete. This ID is returned when creating a scheduled change or can be found using the flag's scheduled changes endpoint. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the feature flag. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the scheduled changes are configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the scheduled changes to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Flag Import Configuration **Slug:** `LAUNCH_DARKLY_DELETE_FLAG_IMPORT_CONFIGURATION` Tool to delete a flag import configuration by ID. The integration key identifies the feature management system from which the import occurs (e.g., 'split'). This action requires the LD-API-Version: beta header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the flag import configuration to delete. | | `integration_key` | string | Yes | The integration key identifying the feature management system from which the import occurs (e.g., 'split'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Flag Link **Slug:** `LAUNCH_DARKLY_DELETE_FLAG_LINK` Permanently deletes a flag link from LaunchDarkly. Flag links connect feature flags to external resources or documentation. Once deleted, the link cannot be recovered. Ensure you have the correct link ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID or Key) of the flag link to delete. This ID is returned when creating a flag link or can be obtained from the list flag links endpoint. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the link to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Integration Configuration **Slug:** `LAUNCH_DARKLY_DELETE_INTEGRATION_CONFIGURATION` Permanently deletes an integration configuration from LaunchDarkly. Integration configurations enable automated workflows with external services like Slack, Datadog, or custom webhooks. Once deleted, the configuration cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `integration_configuration_id` | string | Yes | The unique ID of the integration configuration to delete. This is returned when creating an integration configuration or can be found by listing existing integration configurations. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Account Member **Slug:** `LAUNCH_DARKLY_DELETE_MEMBER` Tool to permanently delete an account member from LaunchDarkly. Use when you need to remove a member's access to the organization. Once deleted, the member will lose all access and need to be re-invited to regain access. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique member ID to delete. This is the member's identifier in LaunchDarkly, not their email address. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Metric **Slug:** `LAUNCH_DARKLY_DELETE_METRIC` Tool to permanently delete a metric from LaunchDarkly. Use when you need to remove a metric that is no longer needed. Once deleted, the metric cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `metric_key` | string | Yes | The unique key of the metric to delete. This is the identifier for the metric within the project. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the metric. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Metric Group **Slug:** `LAUNCH_DARKLY_DELETE_METRIC_GROUP` Tool to permanently delete a metric group from LaunchDarkly. Use when you need to remove a metric group that is no longer needed. Once deleted, the metric group cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the metric group. Use 'List Projects' action to find available project keys. | | `metric_group_key` | string | Yes | The unique key of the metric group to delete. This identifies the specific metric group within the project. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete OAuth 2.0 Client **Slug:** `LAUNCH_DARKLY_DELETE_O_AUTH_CLIENT` Permanently deletes an OAuth 2.0 client from LaunchDarkly. OAuth 2.0 clients are used for programmatic access to the LaunchDarkly API. Once deleted, the client and its credentials cannot be recovered. Ensure you have the correct client ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `clientId` | string | Yes | The unique client ID of the OAuth 2.0 client to delete. This ID is returned when creating an OAuth client or can be found by listing OAuth clients. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Project **Slug:** `LAUNCH_DARKLY_DELETE_PROJECT` Tool to permanently delete a project from LaunchDarkly. Once deleted, the project, its environments, feature flags, and all associated data cannot be recovered. Use with caution and ensure you have the correct project key before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project to delete. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Relay Proxy Auto Configuration **Slug:** `LAUNCH_DARKLY_DELETE_RELAY_AUTO_CONFIG` Tool to delete a Relay Proxy auto configuration by ID. Use when you need to permanently remove a relay proxy configuration from LaunchDarkly. Once deleted, the configuration cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique ID of the Relay Proxy auto configuration to delete. This is returned when creating a relay auto config or can be found by listing existing relay auto configurations. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Release by Flag Key **Slug:** `LAUNCH_DARKLY_DELETE_RELEASE_BY_FLAG_KEY` Tool to delete a release from a feature flag. Use when you need to remove a release associated with a flag in LaunchDarkly. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flag_key` | string | Yes | The unique key of the feature flag from which to delete the release. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Release Pipeline **Slug:** `LAUNCH_DARKLY_DELETE_RELEASE_PIPELINE` Tool to permanently delete a release pipeline from LaunchDarkly. Use when you need to remove a pipeline that is no longer needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the release pipeline. Use 'List Projects' action to find available project keys. | | `pipeline_key` | string | Yes | The unique key of the release pipeline to delete. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Release Policy **Slug:** `LAUNCH_DARKLY_DELETE_RELEASE_POLICY` Tool to permanently delete a release policy from a LaunchDarkly project. Once deleted, the policy cannot be recovered. Requires beta API version header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `policy_key` | string | Yes | The human-readable key of the release policy to delete. This is the unique identifier for the policy within the project. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the release policy. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Repository **Slug:** `LAUNCH_DARKLY_DELETE_REPOSITORY` Tool to delete a code reference repository with the specified name. Use when you need to permanently remove a repository from LaunchDarkly's code references system. Once deleted, the repository and its associated data cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name to delete. This is the unique identifier for the code reference repository in LaunchDarkly. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Segment **Slug:** `LAUNCH_DARKLY_DELETE_SEGMENT` Permanently deletes a segment from LaunchDarkly. Segments are groups of contexts that you can use to manage flag targeting rules. Once deleted, the segment cannot be recovered. Ensure you have the correct segment key before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the segment. Use 'List Projects' action to find available project keys. | | `segment_key` | string | Yes | The unique key of the segment to delete. This identifies the specific segment within the project and environment. | | `environment_key` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Audit Log Subscription **Slug:** `LAUNCH_DARKLY_DELETE_SUBSCRIPTION` Tool to permanently delete an audit log subscription in LaunchDarkly. Audit log subscriptions forward LaunchDarkly audit events to external services like Datadog, Splunk, or Microsoft Teams. Once deleted, the subscription cannot be recovered and audit events will no longer be forwarded to that integration endpoint. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the audit log subscription to delete. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration. | | `integration_key` | string | Yes | The integration key identifying the type of audit log subscription (e.g., 'datadog', 'splunk', 'msteams'). This key determines which integration service the subscription belongs to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Team **Slug:** `LAUNCH_DARKLY_DELETE_TEAM` Permanently deletes a team from LaunchDarkly organization. Once deleted, the team and its associated settings cannot be recovered. Ensure you have the correct team key before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `team_key` | string | Yes | The unique key identifying the team to delete. Use 'List Teams' action to find available team keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Access Token **Slug:** `LAUNCH_DARKLY_DELETE_TOKEN` Tool to permanently delete an access token from LaunchDarkly. Once deleted, the token cannot be recovered and any integrations using it will no longer be able to authenticate. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the access token to delete. This ID is returned when creating a token or can be found using the list tokens endpoint. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Flag Trigger Workflow **Slug:** `LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW` Permanently deletes a flag trigger workflow from LaunchDarkly. Flag triggers allow you to initiate flag changes remotely using a unique webhook URL. Once deleted, the trigger and its URL cannot be recovered. Ensure you have the correct trigger ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the flag trigger to delete. This ID is returned when creating a trigger or can be found using the 'List Flag Triggers' API endpoint. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag trigger. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the trigger is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the trigger to delete. This is the flag the trigger is associated with. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Webhook **Slug:** `LAUNCH_DARKLY_DELETE_WEBHOOK` Tool to delete a webhook from LaunchDarkly. Use when you need to remove an existing webhook integration. Once deleted, the webhook and its configuration cannot be recovered. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the webhook to delete. This ID can be obtained from listing webhooks or when creating a webhook. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Workflow **Slug:** `LAUNCH_DARKLY_DELETE_WORKFLOW` Permanently deletes a workflow from LaunchDarkly. Workflows automate flag changes based on conditions or schedules. Once deleted, the workflow cannot be recovered. Ensure you have the correct workflow ID before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the workflow. Use 'List Projects' action to find available project keys. | | `workflow_id` | string | Yes | The unique identifier (ID) of the workflow to delete. This ID is returned when creating a workflow or can be found using the 'List Workflows' API endpoint. | | `environment_key` | string | Yes | The environment key where the workflow is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the workflow to delete. This is the flag the workflow is associated with. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete Workflow Template **Slug:** `LAUNCH_DARKLY_DELETE_WORKFLOW_TEMPLATE` Permanently deletes a workflow template from LaunchDarkly. Workflow templates provide reusable patterns for common flag change workflows. Once deleted, the template cannot be recovered. Ensure you have the correct template key before proceeding. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `templateKey` | string | Yes | The unique key identifying the workflow template to delete. This is the template key returned when creating a template or found by listing existing workflow templates. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Evaluate Context Instance **Slug:** `LAUNCH_DARKLY_EVALUATE_CONTEXT_INSTANCE` Tool to evaluate flags for a context instance to determine expected flag variations. **Important:** Do not use this as a replacement for LaunchDarkly SDKs in production applications. SDKs are optimized for flag evaluation at scale and generate analytics events. This API is intended for testing, debugging, or administrative purposes only. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | A unique key for the context instance. This identifies the specific context (e.g., user ID, organization ID). | | `kind` | string | Yes | The kind of context instance. Common values include 'user', 'organization', 'device', or custom kinds. | | `sort` | string | No | A comma-separated list of fields to sort by. Fields prefixed by a dash (-) sort in descending order. | | `limit` | integer | No | The number of feature flags to return. Defaults to -1, which returns all flags. Use positive integers to limit results. | | `filter` | string | No | A comma-separated list of filters. Each filter is of the form 'field operator value'. | | `offset` | integer | No | Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment within the project. | | `additional_attributes` | object | No | Additional custom attributes for the context instance (e.g., name, email, custom properties). These attributes can be used in flag targeting rules. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Generate Trust Policy for Data Export **Slug:** `LAUNCH_DARKLY_GENERATE_TRUST_POLICY` Tool to generate an AWS trust policy for Data Export destinations. Use when you need to create or update IAM trust policies that allow LaunchDarkly to assume roles for exporting data to AWS services. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `envKey` | string | Yes | The environment key where the Data Export destination is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `projKey` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get All Holdouts **Slug:** `LAUNCH_DARKLY_GET_ALL_HOLDOUTS` Tool to retrieve all holdouts for a specific project and environment. Use after confirming project and environment keys to list holdout configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The number of holdouts to return in the response. Defaults to 20. | | `offset` | integer | No | Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get All Integration Configurations **Slug:** `LAUNCH_DARKLY_GET_ALL_INTEGRATION_CONFIGURATIONS` Tool to retrieve all integration configurations for a specific integration key. Use when you need to list or audit configurations for integrations like Slack, Datadog, custom approvals, webhooks, or other third-party services. Excludes persistent store and flag import configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `integration_key` | string | Yes | The integration key to filter configurations by. Common values include 'slack', 'datadog', 'jira', 'custom-approvals', 'webhook', etc. This identifies the type of integration. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get All Release Pipelines **Slug:** `LAUNCH_DARKLY_GET_ALL_RELEASE_PIPELINES` Tool to retrieve all release pipelines for a project. Use when you need to view available release pipelines for feature flag releases. Supports filtering and pagination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of release pipelines to return per page. Defaults to 20. | | `filter` | string | No | A comma-separated list of filters. Each filter is of the form field:value. Supported filter fields are described in the API documentation. | | `offset` | integer | No | Number of release pipelines to skip for pagination. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get All Webhooks **Slug:** `LAUNCH_DARKLY_GET_ALL_WEBHOOKS` Tool to retrieve all webhooks configured in the LaunchDarkly account. Use when you need to list, audit, or discover existing webhook integrations. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Announcements Public **Slug:** `LAUNCH_DARKLY_GET_ANNOUNCEMENTS_PUBLIC` Tool to retrieve public announcements from LaunchDarkly. Use to get system announcements, maintenance notices, and updates. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The number of announcements to return. | | `offset` | integer | No | Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query `limit`. | | `status` | string ("active" | "inactive" | "scheduled") | No | Status values for announcement filtering. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Applications **Slug:** `LAUNCH_DARKLY_GET_APPLICATIONS` Tool to retrieve a list of applications in LaunchDarkly. Use to enumerate application keys and metadata. Supports filtering by key, name, kind, and autoAdded status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Sort order and fields. Fields can be comma-separated. Supported fields: 'creationDate', 'name'. Prefix with '-' for descending order. Examples: 'name' (ascending by name), '-name,creationDate' (descending by name, then ascending by creation date). | | `limit` | integer | No | Maximum number of applications to return per page. Defaults to 10 if not specified. | | `expand` | string | No | Comma-separated list of properties to expand in the response. Options: 'flags' (includes flag information for each application). | | `filter` | string | No | Filter expression to narrow results. Supported filters: 'key', 'name', 'kind', and 'autoAdded'. Examples: 'key:my-app', 'kind:browser', 'autoAdded:false'. See https://launchdarkly.com/docs/api/applications-beta#filtering-applications-and-application-versions for syntax details. | | `offset` | integer | No | Number of applications to skip for pagination. Use with 'limit' to paginate through results. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Application Versions **Slug:** `LAUNCH_DARKLY_GET_APPLICATION_VERSIONS` Tool to retrieve all versions for a specific application in LaunchDarkly. Use when you need to list version history or check supported versions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Sort order and fields (comma-separated). Available fields: 'creationDate', 'name'. Prefix with '-' for descending order. Examples: 'name' (ascending by name), '-name,creationDate' (descending by name, then ascending by creation date). | | `limit` | integer | No | Maximum number of versions to return per page. Defaults to 50 if not specified. | | `filter` | string | No | Filter expression to narrow down results. Supported filters: 'key' (version key), 'name' (version name), 'supported' (boolean), 'autoAdded' (boolean). See https://launchdarkly.com/docs/api/applications-beta#filtering-applications-and-application-versions for filter syntax details. | | `offset` | integer | No | Number of versions to skip for pagination. Use with 'limit' for paged results. | | `applicationKey` | string | Yes | The application key identifying the application. This is the unique identifier for the application whose versions you want to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Approval for Flag **Slug:** `LAUNCH_DARKLY_GET_APPROVAL_FOR_FLAG` Tool to get a single approval request for a feature flag in LaunchDarkly. Use when you need detailed information about a specific approval request including its review status, conflicts, and metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The feature flag approval request ID. This ID is returned when creating an approval request or can be found using the approval requests API. | | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key where the approval request exists (e.g., 'test', 'production'). Use GET_ENVIRONMENTS to list available environments. | | `feature_flag_key` | string | Yes | The feature flag key identifying the specific flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Approval Request **Slug:** `LAUNCH_DARKLY_GET_APPROVAL_REQUEST` Tool to get a specific approval request by ID from LaunchDarkly. Use when you need detailed information about a particular approval request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The approval request ID. Example: '697ca6af08d12709fda933a4' | | `expand` | string | No | A comma-separated list of fields to expand in the response. Supported fields may include additional details about members, projects, flags, or environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Approval Requests **Slug:** `LAUNCH_DARKLY_GET_APPROVAL_REQUESTS` Tool to retrieve all approval requests from LaunchDarkly. Use to monitor pending approvals, track approval history, or audit changes requiring approval. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of approval requests to return (1-200). Defaults to 20. | | `expand` | string | No | Comma-separated list of fields to expand in the response. Supported fields may include additional details about members, projects, or flags. | | `filter` | string | No | Filter approval requests using format 'field:value'. Supported fields: 'requestorId' (filter by requestor member ID), 'projectKey' (filter by project), 'notifyMemberIds' (filter by members to notify), 'reviewStatus' (pending, approved, declined), 'status' (pending, applied, declined). Use comma-separated values for multiple filters. Example: 'reviewStatus:pending' or 'projectKey:my-project,status:pending'. | | `offset` | integer | No | Starting index for pagination. Defaults to 0. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Approval Request Settings **Slug:** `LAUNCH_DARKLY_GET_APPROVAL_REQUEST_SETTINGS` Tool to retrieve approval request settings for a project. Use to understand approval requirements for different resource kinds and environments. Supports filtering by environment and resource kind. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | Comma-separated list of fields to expand in the response. Options include 'default' and 'strict'. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `resourceKind` | string | No | Filter approval settings by resource kind (e.g., 'flag', 'segment'). If omitted, returns settings for all resource kinds. | | `environmentKey` | string | No | Filter approval settings by environment key. If omitted, returns settings for all environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Approvals for Flag **Slug:** `LAUNCH_DARKLY_GET_APPROVALS_FOR_FLAG` Tool to retrieve all approval requests for a specific feature flag in an environment. Use when you need to monitor pending approvals or review approval history for a particular flag. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. | | `environmentKey` | string | Yes | The environment key for which to retrieve approval requests. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Audit Log Entries **Slug:** `LAUNCH_DARKLY_GET_AUDIT_LOG_ENTRIES` Tool to get a list of all audit log entries. Use when you need to review account activity, track changes to resources, or audit modifications for compliance purposes. Results can be filtered by date ranges, resource specifiers, or full-text search. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Text to search for. You can search for the full or partial name of the resource. | | `spec` | string | No | A resource specifier that lets you filter audit log listings by resource. See https://launchdarkly.com/docs/home/account/role-resources for syntax details. | | `after` | integer | No | A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries this returns occurred after the timestamp. | | `limit` | integer | No | A limit on the number of audit log entries that return. Set between 1 and 20. The default is 10. | | `before` | integer | No | A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries this returns occurred before the timestamp. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Audit Log Entry **Slug:** `LAUNCH_DARKLY_GET_AUDIT_LOG_ENTRY` Tool to retrieve a single audit log entry by ID. Use when you need to inspect details of a specific audit event. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The ID of the audit log entry to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Big Segment Export **Slug:** `LAUNCH_DARKLY_GET_BIG_SEGMENT_EXPORT` Tool to retrieve a specific big segment export by its ID. Use when you need to check the status or details of a segment export operation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `export_id` | string | Yes | The export ID identifying the specific export to retrieve. | | `project_key` | string | Yes | The project key identifying the project containing the segment. Use 'List Projects' action to find available project keys. | | `segment_key` | string | Yes | The segment key identifying the specific big segment. | | `environment_key` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Big Segment Import **Slug:** `LAUNCH_DARKLY_GET_BIG_SEGMENT_IMPORT` Tool to retrieve the status and details of a big segment import by its ID. Use when you need to check the progress or completion status of an import operation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `import_id` | string | Yes | The unique identifier (ID) of the import to retrieve. | | `project_key` | string | Yes | The project key identifying the project containing the segment. Use LIST_PROJECTS to discover available project keys. | | `segment_key` | string | Yes | The segment key identifying the big segment. | | `environment_key` | string | Yes | The environment key where the segment exists (e.g., 'test', 'production'). Use GET_ENVIRONMENTS to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Big Segment Store Integration **Slug:** `LAUNCH_DARKLY_GET_BIG_SEGMENT_STORE_INTEGRATION` Tool to retrieve a specific persistent store integration for big segments by its ID. Use when you need to inspect the configuration, status, or details of a big segment store integration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the integration. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the big segment store integration to retrieve. | | `environment_key` | string | Yes | The environment key where the integration is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `integration_key` | string ("redis" | "dynamodb") | Yes | The type of big segment store integration, either 'redis' or 'dynamodb'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Big Segment Store Integrations **Slug:** `LAUNCH_DARKLY_GET_BIG_SEGMENT_STORE_INTEGRATIONS` Tool to retrieve all persistent store integrations for big segments. Use when you need to list configured Redis or DynamoDB integrations across all projects and environments. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Branch **Slug:** `LAUNCH_DARKLY_GET_BRANCH` Tool to retrieve branch information from a LaunchDarkly code reference repository. Use to view branch metadata, HEAD commit, sync status, and flag references within the branch. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name. This is the name of the code reference repository configured in LaunchDarkly. | | `branch` | string | Yes | The url-encoded branch name. For branch names with special characters, ensure they are properly URL-encoded. | | `flagKey` | string | No | Filter results to a specific flag key. Only references to this flag will be included. | | `projKey` | string | No | Filter results to a specific project key. Only flag references for this project will be included. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Caller Identity **Slug:** `LAUNCH_DARKLY_GET_CALLER_IDENTITY` Tool to retrieve basic information about the identity used to authenticate API calls. Use when you need to verify authentication credentials or inspect API token details. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Context Attribute Names **Slug:** `LAUNCH_DARKLY_GET_CONTEXT_ATTRIBUTE_NAMES` Tool to retrieve context attribute names for a project and environment. Use when you need to discover available context attributes grouped by context kind. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of items to return in the collection (max: 100, default: 100). | | `filter` | string | No | A comma-separated list of context filters. This endpoint only accepts 'kind' filters with the 'equals' operator, and 'name' filters with the 'startsWith' operator. Example: 'kind equals user,name startsWith email'. See LaunchDarkly docs for filtering contexts syntax. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Context Attribute Values **Slug:** `LAUNCH_DARKLY_GET_CONTEXT_ATTRIBUTE_VALUES` Tool to retrieve unique values for a specific context attribute within a project environment. Use when you need to discover what values exist for a context attribute, optionally filtered by context kind. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of items to return in the collection. Default: 50, Maximum: 100. | | `filter` | string | No | A comma-separated list of context filters. This endpoint only accepts 'kind' filters with the 'equals' operator, and 'value' filters with the 'startsWith' operator. Example: 'kind equals "user"' or 'value startsWith "test"'. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `attributeName` | string | Yes | The name of the context attribute to retrieve values for (e.g., 'key', 'email', 'country'). | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Context Instances **Slug:** `LAUNCH_DARKLY_GET_CONTEXT_INSTANCES` Tool to get context instances for a specific context ID within a project and environment. Use when you need to retrieve context instance data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The context instance ID. Format is typically 'kind:value' (e.g., 'user:test-user-123'). | | `sort` | string | No | Specifies a field by which to sort. LaunchDarkly supports sorting by timestamp in ascending order by specifying 'ts' for this value, or descending order by specifying '-ts'. | | `limit` | integer | No | Specifies the maximum number of context instances to return. Maximum is 50, default is 20. | | `filter` | string | No | A comma-separated list of context filters. This endpoint only accepts an 'applicationId' filter. To learn more about the filter syntax, read Filtering contexts and context instances. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment within the project. | | `continuationToken` | string | No | Limits results to context instances with sort values after the value specified. You can use this for pagination, however, we recommend using the 'next' link instead. | | `includeTotalCount` | boolean | No | Specifies whether to include or omit the total count of matching context instances. Defaults to true. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Context Kinds By Project Key **Slug:** `LAUNCH_DARKLY_GET_CONTEXT_KINDS_BY_PROJECT_KEY` Tool to retrieve all context kinds for a given project. Use when you need to understand available context kinds for targeting and segmentation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Contexts **Slug:** `LAUNCH_DARKLY_GET_CONTEXTS` Tool to retrieve context instances from a LaunchDarkly environment by kind and key. Use when you need to get specific context data for analysis or debugging. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The context key uniquely identifying the context instance within the specified kind. | | `kind` | string | Yes | The context kind (e.g., 'user', 'organization'). 'user' is the default context kind in LaunchDarkly. | | `sort` | string | No | Specifies a field by which to sort. Use 'ts' for ascending order by timestamp, or '-ts' for descending order. | | `limit` | integer | No | Maximum number of context instances to return. Maximum: 50, default: 20. | | `filter` | string | No | A comma-separated list of context filters. This endpoint only accepts an 'applicationId' filter. Example: 'applicationId:com.myapp'. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `continuationToken` | string | No | Limits results to contexts with sort values after the value specified. You can use this for pagination, however, the 'next' link is recommended instead. | | `includeTotalCount` | boolean | No | Whether to include the total count of matching contexts. Defaults to true. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Contexts Clientside Usage **Slug:** `LAUNCH_DARKLY_GET_CONTEXTS_CLIENTSIDE_USAGE` Tool to get a detailed time series of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use this for breakdowns that go beyond the primary-only aggregation of MAU endpoints. The counts reflect data reported by client-side SDKs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. contextKind is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions. | | `sdkName` | array | No | An SDK name to filter results by. Can be specified multiple times to filter by multiple SDK names. | | `anonymous` | array | No | An anonymous value to filter results by. Can be specified multiple times. Valid values: 'true', 'false'. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times to filter by multiple projects. | | `contextKind` | array | No | A context kind to filter results by. Can be specified multiple times to filter by multiple context kinds. | | `granularity` | string ("daily" | "monthly") | No | Data granularity for usage series. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation method for usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Contexts Serverside Usage **Slug:** `LAUNCH_DARKLY_GET_CONTEXTS_SERVERSIDE_USAGE` Tool to get detailed time series of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use for breakdowns beyond primary-only MAU aggregation. The counts reflect data from server-side SDKs. Maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | | `groupBy` | string | No | If specified, returns data for each distinct value of the given field. `contextKind` is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: `projectId`, `environmentId`, `sdkName`, `sdkAppId`, `anonymousV2`. | | `sdkName` | string | No | An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name. | | `anonymous` | string | No | An anonymous value to filter results by. Can be specified multiple times, one query parameter per anonymous value. Valid values: `true`, `false`. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times, one query parameter per project key. | | `contextKind` | string | No | A context kind to filter results by. Can be specified multiple times, one query parameter per context kind. | | `granularity` | string | No | Specifies the data granularity. Defaults to `daily`. Valid values depend on `aggregationType`: **month_to_date** supports `daily` and `monthly`; **incremental** and **rolling_30d** support `daily` only. | | `environmentKey` | string | No | An environment key to filter results by. If specified, exactly one `projectKey` must be provided. Can be specified multiple times, one query parameter per environment key. | | `aggregationType` | string | No | Specifies the aggregation method. Defaults to `month_to_date`. Valid values: `month_to_date`, `incremental`, `rolling_30d`. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Contexts Total Usage **Slug:** `LAUNCH_DARKLY_GET_CONTEXTS_TOTAL_USAGE` Tool to get a detailed time series of the number of context key usages observed by LaunchDarkly in your account, including non-primary context kinds. Use this for breakdowns that go beyond the primary-only aggregation of MAU endpoints. The supported granularity varies by aggregation type, and the maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. contextKind is always included as a grouping dimension. Can be specified multiple times to group data by multiple dimensions. Valid values: projectId, environmentId, sdkName, sdkType, sdkAppId, anonymousV2. | | `sdkName` | array | No | An SDK name to filter results by. Can be specified multiple times to filter by multiple SDK names. | | `sdkType` | array | No | An SDK type to filter results by. Can be specified multiple times to filter by multiple SDK types. | | `anonymous` | array | No | An anonymous value to filter results by. Can be specified multiple times. Valid values: 'true', 'false'. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times to filter by multiple projects. | | `contextKind` | array | No | A context kind to filter results by. Can be specified multiple times to filter by multiple context kinds. | | `granularity` | string ("daily" | "monthly") | No | Data granularity for usage series. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation method for usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Context Instance Segments Membership By Environment **Slug:** `LAUNCH_DARKLY_GET_CTX_INSTANCE_SEGMENTS_MEMBERSHIP` Tool to get segment membership details for a given context instance with attributes. Returns which segments the context belongs to and how (individually targeted or rule-based). Use when you need to understand segment membership for a specific user, organization, or other context type. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The context instance key (unique identifier for the context). | | `kind` | string | Yes | The context kind (e.g., 'user', 'organization', 'device'). Defaults to 'user' if not specified in most SDKs. | | `name` | string | No | An optional human-readable name for the context instance. | | `anonymous` | boolean | No | Whether the context is anonymous. Anonymous contexts are not stored in the LaunchDarkly database. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `customAttributes` | object | No | Optional custom attributes for the context instance. These can be used for segment targeting rules. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Custom Role **Slug:** `LAUNCH_DARKLY_GET_CUSTOM_ROLE` Tool to retrieve a single custom role by key or ID. Use when you need detailed information about a specific role's permissions and policy statements. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `custom_role_key` | string | Yes | The custom role key or ID identifying the specific role to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Custom Roles **Slug:** `LAUNCH_DARKLY_GET_CUSTOM_ROLES` Tool to retrieve a list of all custom roles. Use when you need to list roles for permissions audits or configuration reviews. Note: results are paginated. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of custom roles to return. Defaults to 20. | | `offset` | integer | No | Number of custom roles to skip before returning results. Defaults to 0. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Custom Workflow **Slug:** `LAUNCH_DARKLY_GET_CUSTOM_WORKFLOW` Tool to retrieve details of a specific custom workflow by ID. Use when you need to inspect workflow configuration, stages, execution status, or identify conflicts. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the workflow. Use 'List Projects' action to find available project keys. | | `workflow_id` | string | Yes | The unique identifier (ID) of the custom workflow to retrieve. This ID is returned when creating a workflow or can be found using the 'List Workflows' API endpoint. | | `environment_key` | string | Yes | The environment key where the workflow is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the workflow. This is the flag the workflow is associated with. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Data Export Events Usage **Slug:** `LAUNCH_DARKLY_GET_DATA_EXPORT_EVENTS_USAGE` Tool to retrieve a time series array showing the number of data export events from your account. Use when you need to analyze data export usage patterns over time. The supported granularity varies by aggregation type. The maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: 'environmentId', 'eventKind'. | | `eventKind` | array | No | An event kind to filter results by. Can be specified multiple times, one query parameter per event kind. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times, one query parameter per project key. | | `granularity` | string | No | Specifies the data granularity. Defaults to 'daily'. 'monthly' granularity is only supported with the month_to_date aggregation type. Valid values: 'daily', 'hourly', 'monthly'. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key. | | `aggregationType` | string | No | Specifies the aggregation method. Defaults to 'month_to_date'. Valid values: 'month_to_date', 'incremental'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Dependent Flags **Slug:** `LAUNCH_DARKLY_GET_DEPENDENT_FLAGS` Tool to list dependent feature flags for a specific flag. Use when you need to identify which flags depend on a given feature flag across environments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `feature_flag_key` | string | Yes | The feature flag key for which to retrieve dependent flags. This is the key of the flag whose dependencies you want to list. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Dependent Flags By Environment **Slug:** `LAUNCH_DARKLY_GET_DEPENDENT_FLAGS_BY_ENV` Tool to list dependent flags across all environments for a specified flag. A dependent flag is a flag that uses another flag as a prerequisite. Use when you need to understand flag dependencies. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `featureFlagKey` | string | Yes | The key of the feature flag for which to list dependent flags. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Data Export Destination **Slug:** `LAUNCH_DARKLY_GET_DESTINATION` Tool to retrieve a specific Data Export destination by ID. Use when you need to inspect the configuration details of a destination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the Data Export destination to retrieve. This ID is returned when creating a destination or can be found by listing destinations. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the destination is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Data Export Destinations **Slug:** `LAUNCH_DARKLY_GET_DESTINATIONS` Tool to retrieve all Data Export destinations configured across all projects and environments. Use when you need to list, audit, or discover available data export destinations. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Environment **Slug:** `LAUNCH_DARKLY_GET_ENVIRONMENT` Tool to retrieve a specific environment by project key and environment key. Use when you need detailed information about an environment's configuration and settings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the specific environment to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Environments **Slug:** `LAUNCH_DARKLY_GET_ENVIRONMENTS` Tool to retrieve a list of all environments within a project. Use after confirming the project key; supports pagination. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Field to sort by. Prefix with '-' for descending order. Example: 'name' for ascending, '-name' for descending. | | `limit` | integer | No | Maximum number of environments to return per page. Defaults to 20. | | `filter` | string | No | Filter expression in 'field:value' format. Supported filters include 'query' for text search (e.g., 'query:production'). | | `offset` | integer | No | Number of environments to skip for pagination. Defaults to 0. | | `project_key` | string | Yes | The project key identifying the project containing the environments. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Evaluations Usage **Slug:** `LAUNCH_DARKLY_GET_EVALUATIONS_USAGE` Tool to get time-series arrays of flag evaluation counts, broken down by variation. Use when analyzing flag usage patterns over time. Granularity is automatic: minutely data within 2 hours, hourly within 2 days, otherwise daily. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp. Defaults to the current time if not specified. Format: ISO 8601 timestamp or Unix timestamp in milliseconds. | | `tz` | string | No | The timezone to use for breaks between days when returning daily data. Examples: 'America/New_York', 'UTC', 'Europe/London'. | | `from` | string | No | The series of data returned starts from this timestamp. Defaults to 30 days ago if not specified. Format: ISO 8601 timestamp or Unix timestamp in milliseconds. | | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag to get evaluations usage for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Events Usage **Slug:** `LAUNCH_DARKLY_GET_EVENTS_USAGE` Tool to get time-series arrays of flag evaluation events. Use when analyzing flag usage patterns or tracking evaluation counts broken down by variation. Granularity varies: minutely for data within 2 hours, hourly for within 2 days, otherwise daily. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (ISO 8601 format or Unix timestamp). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (ISO 8601 format or Unix timestamp). Defaults to 24 hours ago. | | `type` | string ("received" | "published") | Yes | The type of event to retrieve. Must be either 'received' or 'published'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Experiment **Slug:** `LAUNCH_DARKLY_GET_EXPERIMENT` Tool to retrieve a specific experiment by project key, environment key, and experiment key. Use when you need detailed information about an experiment's configuration, iterations, and metrics. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Supported values: previousIterations (includes all prior iterations), draftIteration (includes the iteration which has not been started yet), secondaryMetrics (includes secondary metrics), treatments (includes all treatment and parameter details). | | `projectKey` | string | Yes | The project key identifying the project containing the experiment. Use LIST_PROJECTS to discover available project keys. | | `experimentKey` | string | Yes | The experiment key identifying the specific experiment to retrieve. | | `environmentKey` | string | Yes | The environment key identifying the environment containing the experiment. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Experimentation Events Usage **Slug:** `LAUNCH_DARKLY_GET_EXPERIMENTATION_EVENTS_USAGE` Tool to retrieve a time series array showing the number of experimentation events from your account. Use when analyzing experimentation event usage patterns over time. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions. Valid values: environmentId, eventKey, eventKind. | | `eventKey` | array | No | An event key to filter results by. Can be specified multiple times to filter by multiple event keys. | | `eventKind` | array | No | An event kind to filter results by. Can be specified multiple times to filter by multiple event kinds. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times to filter by multiple projects. | | `granularity` | string | No | Specifies the data granularity. Defaults to daily. monthly granularity is only supported with the month_to_date aggregation type. Valid values: daily, hourly, monthly. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times to filter by multiple environments. | | `aggregationType` | string | No | Specifies the aggregation method. Defaults to month_to_date. Valid values: month_to_date, incremental. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Experimentation Keys Usage **Slug:** `LAUNCH_DARKLY_GET_EXPERIMENTATION_KEYS_USAGE` Tool to get a time series showing the number of experimentation keys from your account. Use when you need to track experimentation key usage over time with support for filtering by project, environment, or experiment. Maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | string ("projectId" | "environmentId" | "experimentId") | No | Valid dimensions for grouping experimentation keys usage data. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times for multiple projects. | | `granularity` | string ("daily" | "hourly" | "monthly") | No | Supported granularity levels for experimentation keys usage. | | `experimentId` | string | No | An experiment ID to filter results by. Can be specified multiple times for multiple experiments. | | `environmentKey` | string | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. | | `aggregationType` | string ("month_to_date" | "incremental") | No | Supported aggregation types for experimentation keys usage. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Experimentation Settings **Slug:** `LAUNCH_DARKLY_GET_EXPERIMENTATION_SETTINGS` Tool to retrieve experimentation settings for a project. Use when you need to understand how experiments are configured in a project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Experiments **Slug:** `LAUNCH_DARKLY_GET_EXPERIMENTS` Tool to retrieve experiments from a project and environment. Use after confirming project and environment keys to enumerate experiments and their configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of experiments to return per page. Defaults to 20. | | `expand` | string | No | Comma-separated list of properties that can reveal additional information in the response. Supported fields include metrics, environments, and more. | | `filter` | string | No | Comma-separated list of filters in field:value format. Each filter is of the form field:value. Supported fields include query for text search. | | `offset` | integer | No | Number of experiments to skip for pagination. Use this with limit to page through results. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `lifecycleState` | string | No | Comma-separated list of experiment archived states. Supports 'archived', 'active', or both. Defaults to 'active' experiments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Expiring Context Targets **Slug:** `LAUNCH_DARKLY_GET_EXPIRING_CONTEXT_TARGETS` Tool to retrieve context targets scheduled for removal from a feature flag. Use when you need to check which targets will be automatically removed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys. | | `feature_flag_key` | string | Yes | The feature flag key identifying the flag with expiring targets. Use GET_FEATURE_FLAGS to discover available flag keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Expiring Targets For Segment **Slug:** `LAUNCH_DARKLY_GET_EXPIRING_TARGETS_FOR_SEGMENT` Tool to retrieve context targets scheduled for removal from a segment. Use when you need to check which targets will be automatically removed from a segment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the segment. Use LIST_PROJECTS to discover available project keys. | | `segment_key` | string | Yes | The segment key identifying the segment with expiring targets. | | `environment_key` | string | Yes | The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Extinctions **Slug:** `LAUNCH_DARKLY_GET_EXTINCTIONS` Tool to get a list of all extinctions. LaunchDarkly creates an extinction event after you remove all code references to a flag. Use to discover flags that have been removed from your codebase. To learn more, read [About extinction events](https://launchdarkly.com/docs/home/observability/code-references#about-extinction-events). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | integer | No | Filter results to a specific timeframe based on commit time, expressed as a Unix epoch time in milliseconds. Must be used with `from`. | | `from` | integer | No | Filter results to a specific timeframe based on commit time, expressed as a Unix epoch time in milliseconds. Must be used with `to`. | | `flagKey` | string | No | Filter results to a specific flag key. | | `projKey` | string | No | Filter results to a specific project. | | `repoName` | string | No | Filter results to a specific repository. | | `branchName` | string | No | Filter results to a specific branch. By default, only the default branch will be queried for extinctions. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flag **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAG` Tool to retrieve a specific feature flag by project key and flag key. Use when you need detailed information about a flag's configuration, variations, and targeting rules. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `env` | string | No | Filter configurations by environment. When specified, only environment-specific configuration for that environment will be included in the response. | | `expand` | string | No | A comma-separated list of fields to expand in the response. Supported fields may include specific nested properties. | | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flags **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAGS` Tool to retrieve a list of all feature flags in a project. Use after confirming project key to enumerate flags and their configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `env` | string | No | Filter configurations by environment. Setting this adds environment-specific configuration details to the response. | | `tag` | string | No | Filter feature flags by tag. | | `sort` | string | No | Comma-separated list of fields to sort by. Prefix with '-' for descending order. Examples: 'name', '-creationDate'. | | `limit` | integer | No | Maximum number of feature flags to return. Defaults to 20. | | `expand` | string | No | Comma-separated list of fields to expand in response. Examples: 'evaluation', 'migrationSettings'. | | `filter` | string | No | Comma-separated list of filters in field:value format. Examples: 'archived:true', 'tags:beta', 'query:my-flag'. | | `offset` | integer | No | Number of flags to skip for pagination. Use with limit for paging through results. | | `compare` | boolean | No | Filter to only flags with differences between environments. Deprecated, unavailable in API version 20240415. | | `summary` | boolean | No | By default, flags do not include prerequisites, targets, or rules. Set summary=false and include env parameter to get these details. | | `archived` | boolean | No | Filter to archived or unarchived flags. Deprecated, use filter=archived:true instead. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flag Scheduled Change **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAG_SCHEDULED_CHANGE` Tool to retrieve a specific scheduled change for a feature flag. Use when you need details about a scheduled flag update, including execution time and instructions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The scheduled change ID to retrieve. | | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment for the scheduled change. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flag Status **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUS` Tool to retrieve the status of a feature flag. Returns the current status (new, inactive, active, or launched) along with metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `feature_flag_key` | string | Yes | The feature flag key identifying the specific flag. This is the unique key assigned to the feature flag within the project. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flag Status Across Environments **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUS_ACROSS_ENVIRONMENTS` Tool to retrieve the status of a feature flag across all environments in a project. Use when you need to check flag status across multiple environments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `env` | string | No | Optional environment filter. When specified, returns status only for the specified environment. | | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `feature_flag_key` | string | Yes | The feature flag key identifying the flag to retrieve status for. Use GET_FEATURE_FLAGS to discover available feature flag keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Feature Flag Statuses **Slug:** `LAUNCH_DARKLY_GET_FEATURE_FLAG_STATUSES` Tool to retrieve status information for all feature flags in a project environment. The status includes last request time and state (new, active, inactive, or launched). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key identifying the environment within the project. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Scheduled Changes **Slug:** `LAUNCH_DARKLY_GET_FLAG_CONFIG_SCHEDULED_CHANGES` Tool to retrieve scheduled changes for a feature flag. Use when you need to see planned configuration updates for a flag in a specific environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key where the scheduled changes are configured (e.g., 'production', 'staging'). Use GET_ENVIRONMENTS to list available environments. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag to retrieve scheduled changes for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Defaults by Project **Slug:** `LAUNCH_DARKLY_GET_FLAG_DEFAULTS_BY_PROJECT` Tool to retrieve flag defaults for a specific project. Use when you need to understand the default configuration settings applied to new flags in a project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Followers **Slug:** `LAUNCH_DARKLY_GET_FLAG_FOLLOWERS` Tool to retrieve followers of a flag in a project and environment. Use when you need to see which team members are following a specific feature flag for notifications. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the specific environment. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Import Configuration **Slug:** `LAUNCH_DARKLY_GET_FLAG_IMPORT_CONFIGURATION` Tool to retrieve a single flag import configuration by project key, integration key, and integration ID. Use when you need to inspect the details of a specific flag import configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the flag import configuration to retrieve. | | `integration_key` | string ("split" | "unleash") | Yes | The integration key identifying the feature management system from which the import occurs. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Import Configurations **Slug:** `LAUNCH_DARKLY_GET_FLAG_IMPORT_CONFIGURATIONS` Tool to list all flag import configurations. Use to discover existing configurations for importing flags from external feature management systems. This action requires the LD-API-Version: beta header. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Links **Slug:** `LAUNCH_DARKLY_GET_FLAG_LINKS` Tool to retrieve all flag links for a specific feature flag. Flag links connect feature flags to external resources such as documentation, issue trackers, or code repositories. Use when you need to see what external resources are associated with a flag. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `feature_flag_key` | string | Yes | The unique key of the feature flag to retrieve links for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Followers By Project and Environment **Slug:** `LAUNCH_DARKLY_GET_FOLLOWERS_BY_PROJ_ENV` Tool to retrieve followers of all flags in a given project and environment. Use when you need to see which team members are following which feature flags. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Holdout **Slug:** `LAUNCH_DARKLY_GET_HOLDOUT` Tool to retrieve a specific holdout experiment by project key, environment key, and holdout key. Use when you need detailed information about a holdout experiment configuration, status, and related experiments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Holdout experiment expansion fields have no prefix. Related experiment expansion fields have 'rel-' as a prefix. | | `holdoutKey` | string | Yes | The holdout experiment key to retrieve. | | `projectKey` | string | Yes | The project key identifying the project containing the holdout. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment where the holdout exists. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Integration Configuration **Slug:** `LAUNCH_DARKLY_GET_INTEGRATION_CONFIGURATION` Tool to retrieve a specific integration configuration by ID. Use when you need to inspect the configuration details of an integration with external services like Slack, Datadog, or custom approvals. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `integration_configuration_id` | string | Yes | The unique ID of the integration configuration to retrieve. This is returned when creating an integration configuration or can be found by listing existing integration configurations. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Integration Delivery Configuration by Environment **Slug:** `LAUNCH_DARKLY_GET_INTEGRATION_DELIVERY_CONFIG_BY_ENV` Tool to get delivery configurations by environment for feature store integrations. Use when you need to retrieve integration delivery configurations for a specific project and environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key to retrieve configurations for. Use LIST_PROJECTS to discover available project keys. | | `environment_key` | string | Yes | The environment key to retrieve configurations for. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get IPs **Slug:** `LAUNCH_DARKLY_GET_IPS` Tool to retrieve the list of IP ranges used by the LaunchDarkly service. Use to configure firewall rules that allow LaunchDarkly traffic. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Layers **Slug:** `LAUNCH_DARKLY_GET_LAYERS` Tool to retrieve layers for a project. Use when you need to list all layers or filter by experiment key. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter` | string | No | A comma-separated list of filters. This endpoint only accepts filtering by `experimentKey`. The filter returns layers which include that experiment for the selected environment(s). Example: 'filter=reservations.experimentKey contains expKey'. | | `projectKey` | string | Yes | The project key identifying the project containing the layers. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get MAU Clientside Usage **Slug:** `LAUNCH_DARKLY_GET_MAU_CLIENTSIDE_USAGE` Tool to get a time series of context key usages observed by LaunchDarkly client-side SDKs for the primary context kind. Use when analyzing MAU trends for client applications. The supported granularity varies by aggregation type, and the maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | End timestamp for the time series in Unix milliseconds. Defaults to the current time if not specified. | | `from` | string | No | Start timestamp for the time series in Unix milliseconds. Defaults to the beginning of the current month if not specified. Maximum time range is 365 days. | | `groupBy` | array | No | Group data by specified dimensions. Returns separate time series for each distinct value of the given field(s). Can specify multiple dimensions to create multi-dimensional groupings. | | `sdkName` | array | No | Filter results by SDK name(s). Can specify multiple SDK names to filter by client-side SDK types. | | `anonymous` | array | No | Filter results by anonymous context values. Can specify multiple values to include both anonymous and identified contexts. | | `projectKey` | array | No | Filter results by project key(s). Can specify multiple project keys to include data from multiple projects. | | `granularity` | string ("daily" | "monthly") | No | Valid granularity values for MAU data. | | `environmentKey` | array | No | Filter results by environment key(s). If specified, exactly one projectKey must be provided. Can specify multiple environment keys. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Valid aggregation methods for MAU data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get MAU Total Usage **Slug:** `LAUNCH_DARKLY_GET_MAU_TOTAL_USAGE` Tool to get a time series of the number of context key usages observed by LaunchDarkly in your account, for the primary context kind only. The maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions, one query parameter per dimension. Valid values: projectId, environmentId, sdkName, sdkType, sdkAppId, anonymousV2. | | `sdkName` | array | No | An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name. | | `sdkType` | array | No | An SDK type to filter results by. Can be specified multiple times, one query parameter per SDK type. | | `anonymous` | string | No | An anonymous value to filter results by. Can be specified multiple times, one query parameter per anonymous value. Valid values: 'true', 'false'. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times, one query parameter per project key. | | `granularity` | string ("daily" | "monthly") | No | Data granularity for MAU total usage. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one projectKey must be provided. Can be specified multiple times, one query parameter per environment key. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation type for MAU total usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get MAU Usage **Slug:** `LAUNCH_DARKLY_GET_MAU_USAGE` Tool to get a time-series array of monthly active users (MAU) seen by LaunchDarkly from your account. The granularity is always daily. Note: This endpoint is deprecated and does not return information about active context instances after SDK upgrade to contexts. Use for legacy MAU tracking only. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | ISO 8601 timestamp (e.g., '2024-01-31T23:59:59Z') or Unix epoch in milliseconds. The series of data returned ends at this timestamp. Defaults to the current time if not specified. | | `sdk` | array | No | One or more SDK names to filter results (e.g., 'python-server', 'js-client'). | | `from` | string | No | ISO 8601 timestamp (e.g., '2024-01-01T00:00:00Z') or Unix epoch in milliseconds. The series of data returned starts from this timestamp. Defaults to 30 days ago if not specified. | | `groupby` | array | No | One or more fields to group data by. Returns data for each distinct value of the given field(s). Can group by multiple dimensions (e.g., project and SDK). | | `project` | array | No | One or more project keys to filter results. Specify multiple project keys to view data for multiple projects. | | `sdktype` | array | No | One or more SDK types to filter results. Valid values are 'client' or 'server'. | | `anonymous` | string | No | Filter results to either anonymous or nonanonymous users. Set to 'true' for anonymous users, 'false' for nonanonymous users. | | `contextKind` | array | No | One or more context kinds to filter results. If not set, queries for the 'user' context kind. Specify multiple context kinds to view data for multiple context types. | | `environment` | array | No | One or more environment keys to filter results. When using this parameter, exactly one project key must also be set. Specify multiple environment keys to view data for multiple environments within a single project. | | `aggregationType` | string ("rolling_30d" | "month_to_date" | "daily_incremental") | No | Aggregation type for MAU data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get MAU Usage By Category **Slug:** `LAUNCH_DARKLY_GET_MAU_USAGE_BY_CATEGORY` Tool to get time-series arrays of monthly active users (MAU) by category (browser, mobile, or backend). Use when you need historical MAU metrics broken down by user category. Note: This endpoint is deprecated and does not return information about active context instances. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix epoch milliseconds or ISO 8601 format). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix epoch milliseconds or ISO 8601 format). Defaults to 30 days ago. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Account Member **Slug:** `LAUNCH_DARKLY_GET_MEMBER` Tool to retrieve detailed information about a specific LaunchDarkly account member. Use when you need to view member details, roles, permissions, or team memberships. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique member ID to retrieve. This is the member's identifier in LaunchDarkly. | | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Example: 'teams,roles'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Members **Slug:** `LAUNCH_DARKLY_GET_MEMBERS` Tool to retrieve a list of account members. Use when you need to list members for management, audit, or access control purposes. Supports filtering and pagination. By default, returns the first 20 members. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Comma-separated list of fields to sort by. Prefix with '-' for descending order. Example: 'email' for ascending, '-creationDate' for descending. | | `limit` | integer | No | Maximum number of members to return per page. Defaults to 20. | | `expand` | string | No | Comma-separated list of properties to expand in the response. Can reveal additional information such as teams, roles, or permissions. Example: 'teams,roles'. | | `filter` | string | No | Comma-separated list of filters in 'field:value' format. Supported filters depend on the API documentation. Example: 'role:admin' or 'email:user@example.com'. | | `offset` | integer | No | Number of members to skip for pagination. For example, an offset of 10 skips the first ten items and returns the next items. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Metric **Slug:** `LAUNCH_DARKLY_GET_METRIC` Tool to retrieve a specific metric by project key and metric key. Use when you need detailed information about a metric's configuration, experiments, and usage. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Supported fields are 'experiments', 'experimentCount', 'metricGroups', 'metricGroupCount', 'eventSources', 'guardedRollouts', 'guardedRolloutCount', 'lastUsedInExperiment', and 'lastUsedInGuardedRollout'. | | `versionId` | string | No | The specific version ID of the metric | | `metric_key` | string | Yes | The metric key identifying the specific metric to retrieve. | | `project_key` | string | Yes | The project key identifying the project containing the metric. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Metric Group **Slug:** `LAUNCH_DARKLY_GET_METRIC_GROUP` Tool to retrieve a specific metric group by project key and metric group key. Use when you need detailed information about a metric group's configuration, metrics, and experiments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Supported fields may include experiments and other related resources. | | `project_key` | string | Yes | The project key identifying the project containing the metric group. Use LIST_PROJECTS to discover available project keys. | | `metric_group_key` | string | Yes | The metric group key identifying the specific metric group to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get OAuth 2.0 Client by ID **Slug:** `LAUNCH_DARKLY_GET_O_AUTH_CLIENT_BY_ID` Tool to retrieve a registered OAuth 2.0 client by its unique client ID. Use when you need to view details about an OAuth client including its name, description, and redirect URI. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `clientId` | string | Yes | The unique client ID of the OAuth 2.0 client to retrieve. This ID is returned when creating an OAuth client or can be found by listing OAuth clients. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get OAuth 2.0 Clients **Slug:** `LAUNCH_DARKLY_GET_O_AUTH_CLIENTS` Tool to retrieve all OAuth 2.0 clients registered by your account. Use when you need to list, audit, or manage OAuth clients for API access. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Observability Errors Usage **Slug:** `LAUNCH_DARKLY_GET_OBSERVABILITY_ERRORS_USAGE` Tool to get time-series arrays of the number of observability errors. Supports daily and monthly granularity. Use when you need to analyze error trends over time or monitor observability error counts. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times, one query parameter per project key, to filter by multiple projects. | | `granularity` | string ("daily" | "monthly") | No | Valid granularity values for usage data. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Valid aggregation types for usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Observability Logs Usage **Slug:** `LAUNCH_DARKLY_GET_OBSERVABILITY_LOGS_USAGE` Tool to retrieve time-series arrays of observability logs usage data. Supports daily and monthly granularity with various aggregation methods. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times in the actual API call, one query parameter per project key. | | `granularity` | string ("daily" | "monthly") | No | Granularity type for data aggregation. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation method for usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Observability Sessions Usage **Slug:** `LAUNCH_DARKLY_GET_OBSERVABILITY_SESSIONS_USAGE` Tool to get time-series arrays of the number of observability sessions. Use when analyzing observability usage patterns. Supports 'daily' and 'monthly' granularity. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times for multiple projects. | | `granularity` | string ("daily" | "monthly") | No | Granularity level for observability sessions usage data. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation method for observability sessions usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Observability Traces Usage **Slug:** `LAUNCH_DARKLY_GET_OBSERVABILITY_TRACES_USAGE` Tool to retrieve time-series arrays of observability traces usage data. Supports daily and monthly granularity with various aggregation methods. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | | `projectKey` | string | No | A project key to filter results by. Can be specified multiple times in the actual API call, one query parameter per project key. | | `granularity` | string ("daily" | "monthly") | No | Granularity type for data aggregation. | | `aggregationType` | string ("month_to_date" | "incremental" | "rolling_30d") | No | Aggregation method for usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get OpenAPI Spec **Slug:** `LAUNCH_DARKLY_GET_OPENAPI_SPEC` Tool to retrieve the latest OpenAPI specification for LaunchDarkly's API in JSON format. Use when you need the complete API schema, available endpoints, or integration documentation. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Project **Slug:** `LAUNCH_DARKLY_GET_PROJECT` Tool to retrieve a specific project by project key. Use when you need detailed information about a project's configuration and settings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Supported values: 'environments'. | | `projectKey` | string | Yes | The project key identifying the project to retrieve. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Relay Proxy Config **Slug:** `LAUNCH_DARKLY_GET_RELAY_PROXY_CONFIG` Tool to retrieve a single Relay Proxy auto configuration by ID. Use when you need to inspect the details of a specific relay proxy configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The relay auto config ID. Use this to uniquely identify the Relay Proxy configuration to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Relay Proxy Configs **Slug:** `LAUNCH_DARKLY_GET_RELAY_PROXY_CONFIGS` Tool to retrieve all Relay Proxy configurations in the LaunchDarkly account. Use when you need to list, audit, or manage Relay Proxy configurations. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Release by Flag Key **Slug:** `LAUNCH_DARKLY_GET_RELEASE_BY_FLAG_KEY` Tool to retrieve the currently active release for a feature flag. Use when you need to check release status, phases, and configuration for a specific flag. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flag_key` | string | Yes | The unique key of the feature flag to retrieve the release for. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Release Pipeline by Key **Slug:** `LAUNCH_DARKLY_GET_RELEASE_PIPELINE_BY_KEY` Tool to retrieve a release pipeline by its key. Use when you need detailed information about a release pipeline's configuration, phases, and settings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The unique key identifying the LaunchDarkly project containing the release pipeline. Use 'List Projects' action to find available project keys. | | `pipelineKey` | string | Yes | The unique key of the release pipeline to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Release Policies **Slug:** `LAUNCH_DARKLY_GET_RELEASE_POLICIES` Tool to retrieve a list of release policies for a specified project. Use when you need to view available release automation policies for progressive or guarded rollouts. Requires beta API version header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | | `excludeDefault` | boolean | No | When true, exclude the default release policy from the response. When false or omitted, include the default policy if an environment filter is present. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Release Policy **Slug:** `LAUNCH_DARKLY_GET_RELEASE_POLICY` Tool to retrieve a single release policy by its key for a specified project. Use when you need detailed information about a specific release automation policy. Requires beta API version header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `policy_key` | string | Yes | The release policy key identifying the policy to retrieve. Use GET_RELEASE_POLICIES to discover available policy keys. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get All Release Progressions for Release Pipeline **Slug:** `LAUNCH_DARKLY_GET_RELEASE_PROGRESSIONS_FOR_PIPELINE` Tool to retrieve details on the progression of all releases, across all flags, for a release pipeline. Use when you need to monitor release status, active phases, and completion counts across a pipeline. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The maximum number of items to return. Defaults to 20. | | `filter` | string | No | Accepts filter by 'status' and 'activePhaseId'. 'status' can take a value of 'completed' or 'active'. 'activePhaseId' takes a UUID and will filter results down to releases active on the specified phase. Providing 'status equals completed' along with an 'activePhaseId' filter will return an error as they are disjoint sets of data. The combination of 'status equals active' and 'activePhaseId' will return the same results as 'activePhaseId' alone. | | `offset` | integer | No | Where to start in the list. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `pipelineKey` | string | Yes | The pipeline key identifying the release pipeline. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Repository **Slug:** `LAUNCH_DARKLY_GET_REPOSITORY` Tool to get a single code reference repository by name. Use when you need to retrieve details about a specific repository configured in LaunchDarkly's code references system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name to retrieve. This is the unique identifier for the code reference repository in LaunchDarkly. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Root **Slug:** `LAUNCH_DARKLY_GET_ROOT` Tool to retrieve the LaunchDarkly API root resource. Returns hypermedia links to all available API endpoints. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Root Code Reference Statistic **Slug:** `LAUNCH_DARKLY_GET_ROOT_STATISTIC` Tool to get links to code reference repositories for each project. Use to discover which projects have code references enabled. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Segment **Slug:** `LAUNCH_DARKLY_GET_SEGMENT` Tool to retrieve a specific segment by segment key. Use when you need detailed information about a segment's configuration, targeting rules, and members. Segments are groups of contexts that you can use to manage flag targeting rules. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the segment. Use 'List Projects' action to find available project keys. | | `segmentKey` | string | Yes | The unique key of the segment to retrieve. This identifies the specific segment within the project and environment. | | `environmentKey` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Segment Membership For Context **Slug:** `LAUNCH_DARKLY_GET_SEGMENT_MEMBERSHIP_FOR_CONTEXT` Tool to get big segment membership status for a specific context. Returns whether the context is explicitly included or excluded from the segment. Use when you need to check if a specific user or other context is a member of a big segment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `contextKey` | string | Yes | The context key identifying the specific context (user, organization, etc.) to check segment membership for. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `segmentKey` | string | Yes | The segment key identifying the specific big segment to check membership for. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Segments **Slug:** `LAUNCH_DARKLY_GET_SEGMENTS` Tool to retrieve a list of all segments in a project and environment. Use after confirming project and environment keys to enumerate segments and their configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Comma-separated list of fields to sort by. Prefix with '-' for descending order. Possible fields are 'creationDate', 'name', 'lastModified'. Examples: 'name', '-creationDate'. | | `limit` | integer | No | Maximum number of segments to return. Defaults to 20. | | `filter` | string | No | Filter expression to narrow results. Accepts filter by 'excludedKeys', 'external', 'includedKeys', 'query', 'tags', 'unbounded', 'view'. Example: 'tags:beta'. | | `offset` | integer | No | Number of segments to skip for pagination. Use with limit for paging through results. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key where segments are configured (e.g., 'test', 'production'). Use GET_ENVIRONMENTS to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Service Connections Usage **Slug:** `LAUNCH_DARKLY_GET_SERVICE_CONNECTIONS_USAGE` Tool to get a time series array showing the number of service connection minutes from your account. Use when you need to monitor or analyze service connection usage over time. The supported granularity varies by aggregation type, and the maximum time range is 365 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp (Unix milliseconds). Defaults to the current time. | | `from` | string | No | The series of data returned starts from this timestamp (Unix milliseconds). Defaults to the beginning of the current month. | | `groupBy` | array | No | If specified, returns data for each distinct value of the given field. Can be specified multiple times to group data by multiple dimensions. | | `sdkName` | array | No | An SDK name to filter results by. Can be specified multiple times, one query parameter per SDK name. | | `sdkType` | array | No | An SDK type to filter results by. Can be specified multiple times, one query parameter per SDK type. | | `projectKey` | array | No | A project key to filter results by. Can be specified multiple times, one query parameter per project key. | | `sdkVersion` | array | No | An SDK version to filter results by. Can be specified multiple times, one query parameter per SDK version. | | `granularity` | string ("daily" | "hourly" | "monthly") | No | Data granularity for service connections usage time series. | | `relayVersion` | array | No | A relay version to filter results by. Can be specified multiple times, one query parameter per relay version. | | `connectionType` | array | No | A connection type to filter results by. Can be specified multiple times, one query parameter per connection type. | | `environmentKey` | array | No | An environment key to filter results by. If specified, exactly one `projectKey` must be provided. Can be specified multiple times, one query parameter per environment key. | | `aggregationType` | string ("month_to_date" | "incremental") | No | Aggregation method for service connections usage data. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Code References Statistics **Slug:** `LAUNCH_DARKLY_GET_STATISTICS` Tool to retrieve code references statistics for feature flags. Use when you need to understand where flags are referenced in your codebase. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flagKey` | string | No | Filter results to a specific flag key. If provided, returns statistics only for the specified flag. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Stream Usage **Slug:** `LAUNCH_DARKLY_GET_STREAM_USAGE` Tool to get time-series data of streaming connections to LaunchDarkly. Returns minutely data for requests within the past 2 hours, hourly data for the last 2 days, and daily data otherwise. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp. Defaults to the current time. | | `tz` | string | No | The timezone to use for breaks between days when returning daily data. | | `from` | string | No | The series of data returned starts from this timestamp. Defaults to 30 days ago. | | `source` | string ("client" | "server") | Yes | The source of streaming connections to describe. Must be either 'client' or 'server'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Stream Usage By SDK Version **Slug:** `LAUNCH_DARKLY_GET_STREAM_USAGE_BY_SDK_VERSION` Tool to get time-series data of streaming connections to LaunchDarkly, separated by SDK type and version. Use when you need to analyze connection patterns by SDK version. The granularity varies: minutely data for the past 2 hours, hourly data for the past 2 days, otherwise daily data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | No | The series of data returned ends at this timestamp. Defaults to the current time. Accepts Unix epoch milliseconds or ISO 8601 format. | | `tz` | string | No | The timezone to use for breaks between days when returning daily data. Uses IANA timezone names (e.g., 'America/New_York', 'Europe/London'). | | `sdk` | string | No | If included, this filters the returned series to only those that match this SDK name (e.g., 'node-server-sdk', 'python-server-sdk'). | | `from` | string | No | The series of data returned starts from this timestamp. Defaults to 24 hours ago. Accepts Unix epoch milliseconds or ISO 8601 format. | | `source` | string ("client" | "server") | Yes | The source of streaming connections to describe. Must be either 'client' or 'server'. | | `version` | string | No | If included, this filters the returned series to only those that match this SDK version (e.g., '6.2.0', '7.0.1'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Stream Usage SDK Versions **Slug:** `LAUNCH_DARKLY_GET_STREAM_USAGE_SDK_VERSIONS` Tool to get a list of SDK version objects from LaunchDarkly. Returns all SDKs that have connected from your account in the past 60 days. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `source` | string ("client" | "server") | Yes | The source of streaming connections to describe. Must be either 'client' or 'server'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Audit Log Subscription by ID **Slug:** `LAUNCH_DARKLY_GET_SUBSCRIPTION_BY_ID` Tool to retrieve a specific audit log subscription by ID. Use when you need to inspect the configuration, status, and details of an existing audit log subscription. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the audit log subscription to retrieve. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration. | | `integration_key` | string | Yes | The integration key identifying the type of audit log subscription (e.g., 'slack', 'datadog', 'splunk', 'msteams'). This key determines which integration service the subscription belongs to. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Audit Log Subscriptions by Integration **Slug:** `LAUNCH_DARKLY_GET_SUBSCRIPTIONS` Tool to retrieve all audit log subscriptions for a given integration. Use when you need to list all configured audit log forwarding endpoints for a specific integration type. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `integration_key` | string | Yes | The integration key identifying the type of audit log subscription. Valid values include: 'datadog', 'dynatrace', 'elastic', 'honeycomb', 'logdna', 'msteams', 'new-relic-apm', 'signalfx', 'splunk'. This key determines which integration service type to retrieve subscriptions for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Tags **Slug:** `LAUNCH_DARKLY_GET_TAGS` Tool to retrieve a list of tags from LaunchDarkly. Use when you need to view available tags or filter tags by resource type or prefix. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pre` | string | No | Return tags with the specified prefix. Use this to filter tags that start with a specific string. | | `asOf` | string | No | The time to retrieve tags as of. Default is the current time. Must be a valid ISO 8601 timestamp. | | `kind` | array | No | Fetch tags associated with the specified resource type(s). Options are flag, project, environment, segment, metric, metric-data-source, aiconfig, and view. Returns all types by default. | | `limit` | integer | No | The number of tags to return. Maximum is 1000. Defaults to 20 if not specified. | | `offset` | integer | No | The index of the first tag to return. Default is 0. Use this for pagination. | | `archived` | boolean | No | Whether or not to return archived flags. Only applicable when filtering by flag resource type. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Team **Slug:** `LAUNCH_DARKLY_GET_TEAM` Tool to fetch a specific team by key. Use when you need detailed information about a team's configuration, members, roles, or projects. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. Supported values: 'members' (includes team members), 'roles' (includes custom roles), 'roleAttributes' (includes role attribute mappings), 'projects' (includes projects with write access), 'maintainers' (includes team maintainers). Example: 'members,roles'. | | `teamKey` | string | Yes | The team key identifying the team to retrieve. Use LIST_TEAMS to discover available team keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Team Maintainers **Slug:** `LAUNCH_DARKLY_GET_TEAM_MAINTAINERS2` Tool to retrieve the list of maintainers for a specific LaunchDarkly team. Use when you need to view which members have been assigned as maintainers for a team. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The number of maintainers to return in the response. Defaults to 20. | | `offset` | integer | No | Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query `limit`. | | `teamKey` | string | Yes | The team key identifying the team to retrieve maintainers for. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Team Roles **Slug:** `LAUNCH_DARKLY_GET_TEAM_ROLES` Tool to fetch the custom roles that have been assigned to a team. Use when you need to review team permissions or audit role assignments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The number of roles to return in the response. Defaults to 20. | | `offset` | integer | No | Specifies the starting position for pagination. Defaults to 0. | | `team_key` | string | Yes | The team key to fetch roles for. This is the unique identifier of the team. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Access Token **Slug:** `LAUNCH_DARKLY_GET_TOKEN` Tool to retrieve detailed information about a specific LaunchDarkly access token by its ID. Use when you need to view token details, permissions, or metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The ID of the access token to retrieve. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Tokens **Slug:** `LAUNCH_DARKLY_GET_TOKENS` Tool to fetch a list of all access tokens. Use when you need to list tokens for audit, management, or to find token IDs for other operations. Supports pagination and can retrieve tokens for all members with Admin role. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | The number of access tokens to return in the response. Defaults to 25. | | `offset` | integer | No | Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query limit. | | `showAll` | boolean | No | If set to true, and the authentication access token has the 'Admin' role, personal access tokens for all members will be retrieved. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Trigger by ID **Slug:** `LAUNCH_DARKLY_GET_TRIGGER_WORKFLOW_BY_ID` Tool to retrieve details of a specific flag trigger by ID. Use when you need to inspect trigger configuration, status, or execution history. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the flag trigger to retrieve. This ID is returned when creating a trigger or can be found using the 'List Flag Triggers' API endpoint. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag trigger. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the trigger is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the trigger. This is the flag the trigger is associated with. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Flag Trigger Workflows **Slug:** `LAUNCH_DARKLY_GET_TRIGGER_WORKFLOWS` Tool to retrieve all flag triggers for a specific feature flag in an environment. Use when you need to list existing triggers configured for flag automation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The project key | | `environment_key` | string | Yes | The environment key | | `feature_flag_key` | string | Yes | The feature flag key | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Versions **Slug:** `LAUNCH_DARKLY_GET_VERSIONS` Tool to retrieve LaunchDarkly API version information. Returns the latest API version, list of valid versions, and the version being used for the request. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Webhook **Slug:** `LAUNCH_DARKLY_GET_WEBHOOK` Tool to retrieve a specific webhook by ID. Use when you need to inspect the configuration details of a webhook. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the webhook to retrieve. This ID can be obtained from listing webhooks or when creating a webhook. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Workflows **Slug:** `LAUNCH_DARKLY_GET_WORKFLOWS` Tool to retrieve workflows for a specific feature flag in an environment. Use when you need to list existing workflows configured for flag workflow automation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | A field to sort the items by. Prefix field by a dash ( - ) to sort in descending order. This endpoint supports sorting by `creationDate` or `stopDate`. | | `limit` | integer | No | The maximum number of workflows to return. Defaults to 20. | | `offset` | integer | No | Where to start in the list. Defaults to 0. Use this with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query `limit`. | | `status` | string ("active" | "completed" | "failed") | No | Valid workflow status filter values. | | `project_key` | string | Yes | The project key identifying the project | | `environment_key` | string | Yes | The environment key identifying the environment | | `feature_flag_key` | string | Yes | The feature flag key identifying the specific flag | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get Workflow Templates **Slug:** `LAUNCH_DARKLY_GET_WORKFLOW_TEMPLATES` Tool to retrieve workflow templates belonging to an account. Use when you need to list available templates for workflow automation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `search` | string | No | The substring in either the name or description of a template | | `summary` | boolean | No | Whether the entire template object or just a summary should be returned | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Branches in Code Reference Repository **Slug:** `LAUNCH_DARKLY_LIST_BRANCHES` Tool to list branches in a LaunchDarkly code reference repository. Use this to retrieve all branches that have been synced for a specific repository, including their commit information and sync timestamps. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name to list branches for. This is the name of the code reference repository configured in LaunchDarkly. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Code Reference Repositories **Slug:** `LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES` Lists all code reference repositories configured in LaunchDarkly. Code references allow LaunchDarkly to track where feature flags are used in your codebase. Use this tool to retrieve all connected repositories, optionally filtering by project or flag key. Note: Code references is an Enterprise feature. This endpoint requires write permissions for the code-reference-repository resource. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `flagKey` | string | No | A feature flag key. If provided, filters code references to the specified flag. | | `projKey` | string | No | A LaunchDarkly project key. If provided, filters code reference results to the specified project. | | `withBranches` | string | No | If set to any value, the endpoint returns repositories with associated branch data. | | `withReferencesForDefaultBranch` | string | No | If set to any value, returns repositories with branch data and code references for the default git branch. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Integration Delivery Configurations **Slug:** `LAUNCH_DARKLY_LIST_INTEGRATION_DELIVERY_CONFIGURATIONS` Tool to list all integration delivery configurations. Use when you need to retrieve all configured integrations for feature store capabilities. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Metric Groups **Slug:** `LAUNCH_DARKLY_LIST_METRIC_GROUPS` Tool to retrieve a list of all metric groups in a project. Use when you need to discover available metric groups for experiments or analysis. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | A comma-separated list of fields to sort by. Fields prefixed by a dash ( - ) sort in descending order. Available sort fields vary by endpoint. | | `limit` | integer | No | The number of metric groups to return in the response. Defaults to 20. Maximum limit is 50. | | `expand` | string | No | This parameter is reserved for future use and is not currently supported on this endpoint. | | `filter` | string | No | Filter expression. Accepts filtering by `experimentStatus`, `query`, `kind`, `hasConnections`, `maintainerIds`, and `maintainerTeamKey`. Example: `filter=experimentStatus equals 'running' and query equals 'test'`. | | `offset` | integer | No | Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and returns the next `limit` items. | | `projectKey` | string | Yes | The project key identifying the project containing the metric groups. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Metrics **Slug:** `LAUNCH_DARKLY_LIST_METRICS` Tool to retrieve a list of all metrics in a project. Use when you need to discover available metrics for experiments or analysis. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | A field to sort the items by. Prefix field by a dash ( - ) to sort in descending order. This endpoint supports sorting by `createdAt` or `name`. | | `limit` | integer | No | The number of metrics to return in the response. Defaults to 20. Maximum limit is 50. | | `expand` | string | No | A comma-separated list of properties that can reveal additional information in the response. | | `filter` | string | No | A comma-separated list of filters. This endpoint accepts filtering by `query`, `tags`, 'eventKind', 'isNumeric', 'unitAggregationType`, `hasConnections`, `maintainerIds`, `maintainerTeamKey`, `view`, `dataSourceKeys`, and `metricUsedIn`. | | `offset` | integer | No | Where to start in the list. Use this with pagination. For example, an offset of 10 skips the first ten items and returns the next `limit` items. | | `projectKey` | string | Yes | The project key identifying the project containing the metrics. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Projects **Slug:** `LAUNCH_DARKLY_LIST_PROJECTS` Tool to retrieve a list of all projects. Use after confirming credentials to enumerate project keys and metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Field to sort results by. Use 'name' for ascending or '-name' for descending. Default sorts by creation date. | | `limit` | integer | No | Maximum number of projects to return. Defaults to 20 if not specified. | | `expand` | string | No | Properties to expand in each project response. Use 'environments' to include the list of environments for each project. | | `filter` | string | No | Filter expression in `field:value` format. Supported fields: 'query' (search by name/key), 'tags' (filter by tag), 'keys' (filter by project key). Example: 'query:myproject' or 'keys:proj1,proj2'. | | `offset` | integer | No | Starting index for pagination. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List Teams **Slug:** `LAUNCH_DARKLY_LIST_TEAMS` List all teams in LaunchDarkly organization. Use this tool to retrieve teams for management, audit, or to find team keys for other operations. Supports filtering by name/key and can expand to include member counts, roles, or maintainer information. By default, fetches all teams with automatic pagination. Use 'limit' and 'offset' parameters for manual pagination when dealing with large lists. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `limit` | integer | No | Maximum number of teams to return per page (1-100). If omitted, all teams are fetched automatically with internal pagination. | | `expand` | string | No | Comma-separated list of fields to expand in the response. Options: 'members' (includes member count), 'roles' (includes custom roles), 'projects' (includes projects with write access), 'maintainers' (includes maintainer list), 'roleAttributes' (includes role attribute mappings). Example: 'members,maintainers'. | | `filter` | string | No | Filter teams using format 'field:value'. Supported filters: 'query' (searches team names and keys, case-insensitive), 'nomembers' (boolean, finds teams with zero members). Example: 'query:engineering' or 'nomembers:true'. | | `offset` | integer | No | Number of teams to skip for manual pagination. Use with 'limit' for paged results. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Approval Request Settings **Slug:** `LAUNCH_DARKLY_PATCH_APPROVAL_REQUEST_SETTINGS` Tool to perform a partial update to approval request settings for a project. Use to modify approval requirements for specific environments and resource kinds. Only the fields provided will be updated. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `required` | boolean | No | If approvals are required for this environment. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `serviceKind` | string | No | Which service to use for managing approvals. | | `resourceKind` | string | Yes | The resource kind for which approval settings are being updated (e.g., 'flag', 'segment'). | | `serviceConfig` | object | No | Arbitrary service-specific configuration. | | `environmentKey` | string | Yes | The environment key for which approval settings are being updated. | | `minNumApprovals` | integer | No | Sets the minimum number of approvals required before a member can apply a change. The minimum is one and the maximum is five. | | `canReviewOwnRequest` | boolean | No | Allow someone who makes an approval request to apply their own change. | | `requiredApprovalTags` | array | No | Require approval only on flags with the provided tags. Otherwise all flags will require approval. | | `canApplyDeclinedChanges` | boolean | No | Allow applying the change as long as at least one person has approved. | | `autoApplyApprovedChanges` | boolean | No | Automatically apply changes that have been approved by all reviewers. This field is only applicable for approval services other than LaunchDarkly. | | `serviceKindConfigurationId` | string | No | Optional integration configuration ID of a custom approval integration. This is an Enterprise-only feature. | | `bypassApprovalsForPendingChanges` | boolean | No | Whether to skip approvals for pending changes. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Big Segment Store Integration **Slug:** `LAUNCH_DARKLY_PATCH_BIG_SEGMENT_STORE_INTEGRATION` Tool to update a persistent store integration for big segments using JSON Patch operations. Use when you need to modify integration settings like name, enabled status, or configuration details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the integration. Each operation modifies a specific field like name, on, config, or tags. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `project_key` | string | Yes | The project key identifying the project containing the integration. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the big segment store integration to update. | | `environment_key` | string | Yes | The environment key where the integration is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `integration_key` | string ("redis" | "dynamodb") | Yes | The type of big segment store integration, either 'redis' or 'dynamodb'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Custom Role **Slug:** `LAUNCH_DARKLY_PATCH_CUSTOM_ROLE` Tool to update a custom role's settings using JSON Patch operations. Use when you need to modify role configuration like name, description, or policy statements. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the custom role. Each operation modifies a specific field like name, description, policy, or basePermissions. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `comment` | string | No | Optional comment describing the reason for the update. | | `customRoleKey` | string | Yes | The custom role key identifying the specific role to update. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Data Export Destination **Slug:** `LAUNCH_DARKLY_PATCH_DESTINATION` Tool to update a Data Export destination using JSON Patch operations. Use when you need to modify destination settings like enabling/disabling the export, changing the name, or updating configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the Data Export destination to update. This ID is returned when creating a destination or can be found by listing destinations. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `environment_key` | string | Yes | The environment key where the destination is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `patch_operations` | array | Yes | An array of JSON Patch operations to apply to the destination. Each operation modifies a specific field. Common paths: '/on' (boolean - enable/disable), '/name' (string), '/config' (object). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Environment **Slug:** `LAUNCH_DARKLY_PATCH_ENVIRONMENT` Tool to update an environment's settings using JSON Patch operations. Use when you need to modify environment configuration like name, color, approval settings, or behavior flags. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the environment. Each operation modifies a specific field like name, color, confirmChanges, requireComments, tags, critical, defaultTtl, secureMode, or defaultTrackEvents. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `projectKey` | string | Yes | The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the specific environment to update. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Experiment **Slug:** `LAUNCH_DARKLY_PATCH_EXPERIMENT` Tool to update an experiment using semantic patch format. Use when you need to modify experiment properties like name, description, or manage iterations (start/stop). Requires Content-Type header with domain-model=launchdarkly.semanticpatch. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the purpose or reason for these changes. Useful for audit trails and team communication. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project containing the experiment. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of instruction objects specifying the changes to apply to the experiment. Each instruction has a 'kind' field indicating the operation type and an optional 'value' field for the operation's data. | | `experimentKey` | string | Yes | The unique key identifying the experiment to update. | | `environmentKey` | string | Yes | The environment key where the experiment is located. Common values include 'production', 'staging', 'test'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Expiring Targets **Slug:** `LAUNCH_DARKLY_PATCH_EXPIRING_TARGETS` Tool to update expiring context targets on a feature flag. Use when you need to add, update, or remove scheduled target expirations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the change. This will be recorded in the audit log. | | `project_key` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of instructions to apply to the expiring targets. Each instruction specifies an operation (add, update, or remove) and the associated target details. Multiple instructions can be provided to perform batch updates. | | `environment_key` | string | Yes | The environment key identifying the environment where targets are expiring. Use GET_ENVIRONMENTS to discover available environment keys. | | `feature_flag_key` | string | Yes | The feature flag key identifying the flag with expiring targets. Use GET_FEATURE_FLAGS to discover available flag keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Feature Flag **Slug:** `LAUNCH_DARKLY_PATCH_FEATURE_FLAG` Tool to update a feature flag's settings using JSON Patch operations. Use when you need to modify flag configuration like description, name, tags, archived status, or other flag properties. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the feature flag. Each operation modifies a specific field like description, name, tags, temporary, archived, or maintainerId. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `dryRun` | boolean | No | If true, the patch will be validated but not persisted. Returns a preview of the flag after the patch is applied without making actual changes. Useful for testing patch operations. | | `comment` | string | No | Optional comment to describe the reason for the change or provide context about the update. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `featureFlagKey` | string | Yes | The feature flag key identifying the flag to update. The key identifies the flag in your code. | | `ignoreConflicts` | boolean | No | If true, the patch will be applied even if it causes a pending scheduled change or approval request to fail. Defaults to false if not specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Flag Config Approval Request **Slug:** `LAUNCH_DARKLY_PATCH_FLAG_CONFIG_APPROVAL_REQUEST` Tool to perform a partial update to a flag config approval request using semantic patch format. Use when you need to add reviewers to an approval request. Requires special headers: Content-Type with domain-model=launchdarkly.semanticpatch and LD-API-Version: beta. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The approval request ID to update. Use GET_APPROVALS_FOR_FLAG to retrieve approval request IDs. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of semantic patch instruction objects specifying the changes to apply to the approval request. Each instruction has a 'kind' field and relevant parameters. | | `environmentKey` | string | Yes | The environment key where the approval request exists. Common values include 'production', 'staging', 'test'. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag with the approval request. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Flag Scheduled Change **Slug:** `LAUNCH_DARKLY_PATCH_FLAG_CONFIG_SCHEDULED_CHANGE` Tool to update a scheduled change workflow for a feature flag. Use when you need to modify the execution time or instructions of an existing scheduled change. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier of the scheduled change to update. Use GET_FLAG_CONFIG_SCHEDULED_CHANGES to list available scheduled changes and their IDs. | | `comment` | string | No | Optional comment describing the update to the scheduled change. Useful for audit trails and team communication. | | `projectKey` | string | Yes | The project key identifying the project containing the feature flag. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of semantic patch instructions to apply to the scheduled change. Each instruction must have a 'kind' field specifying the operation type (e.g., 'updateScheduledChangesExecutionDate', 'replaceScheduledChangesInstructions') and additional fields as required by that instruction type. For updateScheduledChangesExecutionDate, include 'value' as a Unix timestamp in milliseconds. | | `environmentKey` | string | Yes | The environment key where the scheduled change is configured (e.g., 'production', 'staging'). Use GET_ENVIRONMENTS to list available environments. | | `featureFlagKey` | string | Yes | The feature flag key identifying the specific flag with the scheduled change to update. | | `ignoreConflicts` | boolean | No | Whether to succeed (true) or fail (false) when these new instructions conflict with existing scheduled changes. Defaults to false if not specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Flag Defaults By Project **Slug:** `LAUNCH_DARKLY_PATCH_FLAG_DEFAULTS_BY_PROJECT` Tool to update flag defaults for a project using JSON Patch operations. Use when you need to modify default settings that apply to new flags created in the project, such as tags, temporary status, boolean variation names, or client-side availability. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the flag defaults. Each operation modifies fields like tags, temporary, booleanDefaults, or defaultClientSideAvailability. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Flag Import Configuration **Slug:** `LAUNCH_DARKLY_PATCH_FLAG_IMPORT_CONFIGURATION` Tool to update a flag import configuration using JSON Patch operations. Use when you need to modify configuration settings like name, tags, or config values. To add to array fields, use '/' where '/0' adds to beginning and '/-' adds to end. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the flag import configuration. You can update the 'config', 'tags', and 'name' fields. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the flag import configuration to update. | | `integration_key` | string ("split" | "unleash") | Yes | The integration key identifying the feature management system from which the import occurs. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Holdout **Slug:** `LAUNCH_DARKLY_PATCH_HOLDOUT` Tool to update a LaunchDarkly holdout using semantic patch operations. Use when you need to modify a holdout's name, description, or end the holdout. Requires LD-API-Version: beta header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the update. | | `holdoutKey` | string | Yes | The holdout key identifying the holdout to update. | | `projectKey` | string | Yes | The project key identifying the project containing the holdout. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of semantic patch instructions to apply to the holdout. Instructions are applied in order. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Account Member **Slug:** `LAUNCH_DARKLY_PATCH_MEMBER` Tool to modify an account member's information using JSON Patch operations. Use when you need to update member details like name, role, custom roles, or other member attributes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique member ID to modify. This is the member's identifier in LaunchDarkly. | | `patch` | array | Yes | Array of JSON Patch operations to apply to the member. Each operation modifies a specific field like firstName, lastName, role, or customRoles. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Members **Slug:** `LAUNCH_DARKLY_PATCH_MEMBERS` Tool to perform partial updates to multiple LaunchDarkly account members using semantic patch format. Use when you need to bulk update member roles or attributes. Supports updating specific members by ID or all members matching filter criteria. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the update. | | `instructions` | array | Yes | Array of instruction objects for updating members. Each instruction specifies an operation type (replaceMembersRoles, replaceAllMembersRoles, replaceMembersCustomRoles, replaceAllMembersCustomRoles, or replaceMembersRoleAttributes) and the parameters for that operation. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Metric **Slug:** `LAUNCH_DARKLY_PATCH_METRIC` Tool to update a metric's settings using JSON Patch operations. Use when you need to modify metric configuration like description, name, tags, or other properties. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the metric. Each operation modifies a specific field like description, name, tags, or other metric properties. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `metricKey` | string | Yes | The metric key identifying the specific metric to update. | | `projectKey` | string | Yes | The project key identifying the project containing the metric. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Metric Group **Slug:** `LAUNCH_DARKLY_PATCH_METRIC_GROUP` Tool to update a metric group's settings using JSON Patch operations. Use when you need to modify metric group configuration like description, name, tags, or other properties. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the metric group. Each operation modifies a specific field like description, name, tags, or other metric group properties. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `projectKey` | string | Yes | The project key identifying the project containing the metric group. Use LIST_PROJECTS to discover available project keys. | | `metricGroupKey` | string | Yes | The metric group key identifying the specific metric group to update. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch OAuth 2.0 Client **Slug:** `LAUNCH_DARKLY_PATCH_O_AUTH_CLIENT` Tool to update an existing OAuth 2.0 client in LaunchDarkly using JSON Patch operations. Use when you need to modify OAuth client details like name, description, or redirect URI. Only 'name', 'description', and 'redirectUri' fields may be patched. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `clientId` | string | Yes | The unique client ID of the OAuth 2.0 client to patch. This ID is returned when creating an OAuth client or can be found by listing OAuth clients. | | `patchOperations` | array | Yes | An array of JSON Patch operations to apply to the OAuth client. Each operation modifies a specific field. Only 'name', 'description', and 'redirectUri' may be patched. Common paths: '/name', '/description', '/redirectUri'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Project **Slug:** `LAUNCH_DARKLY_PATCH_PROJECT` Tool to update a LaunchDarkly project using JSON Patch operations (RFC 6902). Use when you need to modify specific fields of a project such as name, tags, client-side availability settings, or other project configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the project. Operations are applied in order. Common paths: '/name' (project name), '/tags' (project tags), '/includeInSnippetByDefault' (client-side availability), '/defaultClientSideAvailability/usingMobileKey', '/defaultClientSideAvailability/usingEnvironmentId'. | | `projectKey` | string | Yes | The project key identifying the project to update. Use LIST_PROJECTS to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Relay Proxy Config **Slug:** `LAUNCH_DARKLY_PATCH_RELAY_AUTO_CONFIG` Tool to update a Relay Proxy auto configuration using JSON Patch operations (RFC 6902). Use when you need to modify specific fields of a relay proxy configuration such as name, policy, or other settings. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The relay auto config ID. Use this to uniquely identify the Relay Proxy configuration to update. | | `patch` | array | Yes | Array of JSON Patch operations to apply to the Relay Proxy configuration. Operations are applied in order. | | `comment` | string | No | Optional comment describing the reason for this change. Useful for audit trail and team communication. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Repository **Slug:** `LAUNCH_DARKLY_PATCH_REPOSITORY` Tool to update a code reference repository's settings using JSON Patch operations. Use when you need to modify repository configuration like default branch, enabled status, or URL templates. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `repo` | string | Yes | The repository name to update. This is the unique identifier for the code reference repository in LaunchDarkly. | | `patch` | array | Yes | Array of JSON Patch operations to apply to the repository. Each operation modifies a specific field like defaultBranch, enabled, commitUrlTemplate, or hunkUrlTemplate. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Segment **Slug:** `LAUNCH_DARKLY_PATCH_SEGMENT` Tool to update a segment's settings using JSON Patch operations. Use when you need to modify segment configuration like description, name, tags, included/excluded targets, or targeting rules. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patch` | array | Yes | Array of JSON Patch operations to apply to the segment. Each operation modifies a specific field like description, name, tags, included, excluded, or rules. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | | `dryRun` | boolean | No | If true, the patch will be validated but not persisted. Returns a preview of the segment after the patch is applied without making actual changes. Useful for testing patch operations. | | `comment` | string | No | Optional comment to describe the reason for the change or provide context about the update. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project containing the segment. Use LIST_PROJECTS to discover available project keys. | | `segmentKey` | string | Yes | The unique key of the segment to update. This identifies the specific segment within the project and environment. | | `environmentKey` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use GET_ENVIRONMENTS to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Team **Slug:** `LAUNCH_DARKLY_PATCH_TEAM` Tool to perform partial updates to a LaunchDarkly team using semantic patch format. Use when you need to update team properties (name, description), manage team members, or modify role attributes. Supports atomic updates with multiple instructions applied together. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the update for audit purposes. | | `team_key` | string | Yes | The unique key identifying the team to update. Use 'List Teams' action to find available team keys. | | `instructions` | array | Yes | Array of instruction objects for updating the team. Each instruction specifies an operation type (e.g., updateDescription, addMembers, removeMembers, updateName) and the parameters for that operation. Multiple instructions can be provided and will be applied atomically. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Teams **Slug:** `LAUNCH_DARKLY_PATCH_TEAMS` Tool to perform partial updates to multiple LaunchDarkly teams using semantic patch format. Use when you need to bulk add members to multiple teams at once. Supports adding specific members by ID or all members matching filter criteria to teams. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the update. | | `instructions` | array | Yes | Array of instruction objects for updating teams. Each instruction specifies an operation type (addMembersToTeams or addAllMembersToTeams) and the parameters for that operation. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Patch Access Token **Slug:** `LAUNCH_DARKLY_PATCH_TOKEN` Tool to update an access token's settings using JSON Patch operations. Use when you need to modify token properties like name, description, role, or custom role IDs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the access token to update. This ID is returned when creating a token or can be found using the list tokens endpoint. | | `patch` | array | Yes | Array of JSON Patch operations to apply to the access token. Each operation modifies a specific field like name, description, role, customRoleIds, or defaultApiVersion. See https://datatracker.ietf.org/doc/html/rfc6902 for JSON Patch specification. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Flag Trigger **Slug:** `LAUNCH_DARKLY_PATCH_TRIGGER_WORKFLOW` Tool to update a flag trigger using semantic patch operations. Use when you need to enable/disable a trigger or modify its configuration. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the flag trigger to update. This ID is returned when creating a trigger or can be found using the 'Get Trigger Workflow by ID' action. | | `comment` | string | No | Optional comment describing the reason for this update. Useful for audit trail and team communication. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag trigger. Use 'List Projects' action to find available project keys. | | `instructions` | array | Yes | Array of semantic patch instructions to apply to the trigger. Each instruction specifies an operation like disabling/enabling the trigger or updating its flag actions. | | `environment_key` | string | Yes | The environment key where the trigger is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the trigger to update. This is the flag the trigger is associated with. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Webhook **Slug:** `LAUNCH_DARKLY_PATCH_WEBHOOK` Tool to update a LaunchDarkly webhook using JSON Patch operations (RFC 6902). Use when you need to modify webhook settings such as name, URL, enabled status, tags, or secret. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the webhook to update. This ID can be obtained from listing webhooks or when creating a webhook. | | `patch` | array | Yes | Array of JSON Patch operations to apply to the webhook. Operations are applied in order. Common paths: '/name' (webhook name), '/url' (webhook URL), '/on' (enable/disable webhook), '/tags' (webhook tags), '/secret' (webhook secret). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create or Update Flag Defaults by Project **Slug:** `LAUNCH_DARKLY_PUT_FLAG_DEFAULTS_BY_PROJECT` Tool to create or update flag defaults for a specific project. Use when you need to configure default settings that will be applied to new flags created in the project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `tags` | array | Yes | A list of default tags for each flag. | | `temporary` | boolean | Yes | Whether the flag should be temporary by default. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `booleanDefaults` | object | Yes | Default settings for boolean flags. | | `defaultClientSideAvailability` | object | Yes | Default client-side SDK availability settings for new flags. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Reset Environment Mobile Key **Slug:** `LAUNCH_DARKLY_RESET_ENVIRONMENT_MOBILE_KEY` Tool to reset the mobile SDK key for a specific environment. Use when you need to generate a new mobile key for security purposes or after a key compromise. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the specific environment whose mobile key should be reset. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Reset Environment SDK Key **Slug:** `LAUNCH_DARKLY_RESET_ENVIRONMENT_SDK_KEY` Tool to reset the SDK key for a specific environment. Use when you need to rotate keys for security or revoke access. The new SDK key is returned in the response. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `expiry` | integer | No | The time at which you want the old SDK key to expire, in UNIX milliseconds. By default, the key expires immediately. During the period between this call and the time when the old SDK key expires, both the old SDK key and the new SDK key will work. | | `projectKey` | string | Yes | The project key identifying the project containing the environment. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the specific environment whose SDK key should be reset. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Reset Relay Proxy Configuration Key **Slug:** `LAUNCH_DARKLY_RESET_RELAY_AUTO_CONFIG` Tool to reset the Relay Proxy configuration key. Use when you need to rotate or regenerate the configuration key for security purposes. The old key will expire immediately by default, or at the time specified in the expiry parameter. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The Relay Proxy configuration ID. Use this to uniquely identify the configuration whose key should be reset. | | `expiry` | integer | No | An expiration time for the old Relay Proxy configuration key, expressed as a Unix epoch time in milliseconds. By default, the old key will expire immediately. Provide a future timestamp to allow gradual transition to the new key. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Reset Access Token **Slug:** `LAUNCH_DARKLY_RESET_TOKEN` Tool to reset a LaunchDarkly access token, generating a new token value. Use when you need to rotate tokens for security or revoke access to the old token. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The ID of the access token to update. | | `expiry` | integer | No | An expiration time for the old token key, expressed as a Unix epoch time in milliseconds. By default, the token will expire immediately. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search Audit Log Entries **Slug:** `LAUNCH_DARKLY_SEARCH_AUDIT_LOG_ENTRIES` Search audit log entries in LaunchDarkly. Use to find specific actions, changes, or events by filtering with resource specifiers, date ranges, and full-text search. Resource specifiers follow LaunchDarkly's resource specifier syntax (e.g., 'proj/*' for all projects). #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `q` | string | No | Text to search for. You can search for the full or partial name of the resource. | | `after` | integer | No | A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries returned occurred after this timestamp. | | `limit` | integer | No | A limit on the number of audit log entries that return. Set between 1 and 20. The default is 10. | | `before` | integer | No | A timestamp filter, expressed as a Unix epoch time in milliseconds. All entries returned occurred before this timestamp. | | `resource_specifiers` | array | Yes | Array of resource specifier statements that filter audit log entries by resources and actions. Each statement defines what resources and actions to include or exclude. At least one resource specifier is required. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search Context Instances **Slug:** `LAUNCH_DARKLY_SEARCH_CONTEXT_INSTANCES` Tool to search for context instances within a project and environment. Use when you need to find and retrieve context instances with filtering and pagination support. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Specifies a field by which to sort. LaunchDarkly supports sorting by timestamp in ascending order by specifying 'ts' for this value, or descending order by specifying '-ts'. | | `limit` | integer | No | Specifies the maximum number of items in the collection to return (max: 50, default: 20). | | `filter` | string | No | A comma-separated list of context filters. This endpoint only accepts an 'applicationId' filter. To learn more about the filter syntax, read Filtering contexts and context instances. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment within the project. | | `continuationToken` | string | No | Limits results to context instances with sort values after the value specified. You can use this for pagination, however, we recommend using the 'next' link instead. | | `includeTotalCount` | boolean | No | Specifies whether to include or omit the total count of matching context instances. Defaults to true. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Search Contexts **Slug:** `LAUNCH_DARKLY_SEARCH_CONTEXTS` Tool to search for contexts in a LaunchDarkly environment with flexible filtering and sorting. Use when you need to find contexts matching specific criteria or patterns. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort` | string | No | Specifies a field by which to sort. Use 'ts' for ascending order by timestamp, or '-ts' for descending order. | | `limit` | integer | No | Specifies the maximum number of items in the collection to return. Maximum: 50, default: 20. | | `filter` | string | No | A comma-separated list of context filters. To learn more about the filter syntax, read Filtering contexts and context instances documentation. | | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `environmentKey` | string | Yes | The environment key identifying the environment. Use GET_ENVIRONMENTS to discover available environment keys. | | `continuationToken` | string | No | Limits results to contexts with sort values after the value specified. You can use this for pagination, however, the 'next' link is recommended instead. | | `includeTotalCount` | boolean | No | Specifies whether to include or omit the total count of matching contexts. Defaults to true. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Trigger Flag Import Job **Slug:** `LAUNCH_DARKLY_TRIGGER_FLAG_IMPORT_JOB` Tool to trigger a single flag import run for an existing flag import configuration. Use when you need to manually initiate a flag import from an external feature management system. This action requires the LD-API-Version: beta header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `integration_id` | string | Yes | The unique identifier (ID) of the flag import configuration to trigger. | | `integration_key` | string | Yes | The integration key identifying the feature management system from which the import occurs (e.g., 'split'). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Announcement **Slug:** `LAUNCH_DARKLY_UPDATE_ANNOUNCEMENT_PUBLIC` Tool to update an existing announcement in LaunchDarkly using JSON Patch operations. Use when you need to modify announcement details like title, message, severity, or timing. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `announcementId` | string | Yes | The unique identifier of the announcement to update. This ID is returned when creating an announcement or can be retrieved by listing announcements. | | `patchOperations` | array | Yes | An array of JSON Patch operations to apply to the announcement. Each operation modifies a specific field. Common paths: '/title', '/message', '/severity', '/startTime', '/endTime', '/isDismissible'. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Big Segment Context Targets **Slug:** `LAUNCH_DARKLY_UPDATE_BIG_SEGMENT_CONTEXT_TARGETS` Tool to update context targets included or excluded in a big segment. Big segments include larger list-based segments and synced segments. Use this when you need to add or remove specific context targets (users, organizations, etc.) from a big segment's inclusion or exclusion lists. This operation does not support standard segments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `excluded` | object | No | Context target modification specification for add/remove operations. | | `included` | object | No | Context target modification specification for add/remove operations. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the segment. Use 'List Projects' action to find available project keys. | | `segment_key` | string | Yes | The unique key of the big segment to update. This operation only supports big segments (larger list-based segments and synced segments), not standard segments. | | `environment_key` | string | Yes | The environment key where the segment is configured (e.g., 'test', 'production'). Use 'Get Environments' action to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Context Flag Setting **Slug:** `LAUNCH_DARKLY_UPDATE_CONTEXT_FLAG_SETTING` Tool to enable or disable a feature flag for a specific context based on its context kind and key. Use when you need to set a custom flag variation for an individual context (user, organization, device, etc.). The setting value must match the flag's variation type. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the reason for this change. | | `setting` | string | No | The variation value to set for the context. Must match the flag's variation type (boolean, string, number, JSON, etc.). For boolean flags, use true or false. For string flags, use the exact variation value string. Omit this field or set to null to erase the context's custom setting and revert to default targeting behavior. | | `context_key` | string | Yes | The context key identifying the specific context instance (e.g., user ID, organization ID). | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use LIST_PROJECTS to discover available project keys. | | `context_kind` | string | Yes | The context kind (e.g., 'user', 'organization', 'device'). Context kinds define the type of entity you're targeting. | | `featureFlagKey` | string | Yes | The feature flag key identifying the flag to configure for this context. | | `environment_key` | string | Yes | The environment key where the flag is configured (e.g., 'test', 'production'). Use GET_ENVIRONMENTS to list available environments. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create or Update Context Kind **Slug:** `LAUNCH_DARKLY_UPDATE_CONTEXT_KIND` Tool to create or update a context kind in a LaunchDarkly project. Use this to define custom context types for feature flag targeting beyond the default user context. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `key` | string | Yes | The context kind key to create or update. | | `name` | string | Yes | The context kind name. This is the display name for the context kind. | | `version` | integer | No | The context kind version. If not specified when the context kind is created, defaults to 1. | | `archived` | boolean | No | Whether the context kind is archived. Archived context kinds are unavailable for targeting. | | `projectKey` | string | Yes | The project key. Use LIST_PROJECTS to discover available project keys. | | `description` | string | No | The context kind description. Provides additional context about the purpose of this context kind. | | `hideInTargeting` | boolean | No | Alias for archived. Whether to hide this context kind in targeting. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Experimentation Settings **Slug:** `LAUNCH_DARKLY_UPDATE_EXPERIMENTATION_SETTINGS` Tool to update experimentation settings for a project. Use when you need to configure randomization units for experiments in a project. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `projectKey` | string | Yes | The project key identifying the project. Use LIST_PROJECTS to discover available project keys. | | `randomizationUnits` | array | Yes | An array of randomization units allowed for this project. At least one unit must be specified. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Flag Link **Slug:** `LAUNCH_DARKLY_UPDATE_FLAG_LINK` Tool to update an existing flag link in LaunchDarkly using JSON Patch operations. Use when you need to modify flag link details like title or description. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier of the flag link to update. This ID is returned when creating a flag link or can be obtained from the list flag links endpoint. | | `project_key` | string | Yes | The project key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `feature_flag_key` | string | Yes | The unique key of the feature flag that has the link to update. | | `patch_operations` | array | Yes | An array of JSON Patch operations to apply to the flag link. Each operation modifies a specific field. Common paths: '/title' to update the link title, '/description' to update the link description. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Integration Configuration **Slug:** `LAUNCH_DARKLY_UPDATE_INTEGRATION_CONFIGURATION` Tool to update an existing integration configuration in LaunchDarkly using JSON Patch operations. Use when you need to modify integration details like name, enabled status, tags, or configuration values. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `patchOperations` | array | Yes | An array of JSON Patch operations to apply to the integration configuration. Each operation modifies a specific field. Common paths: '/name', '/enabled', '/tags', '/configValues', '/capabilityConfig'. | | `integrationConfigurationId` | string | Yes | The unique ID of the integration configuration to update. This is returned when creating an integration configuration or can be found by listing existing integration configurations. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Layer **Slug:** `LAUNCH_DARKLY_UPDATE_LAYER` Tool to update a layer using semantic patch instructions. Use when you need to modify layer properties like name, description, or experiment reservations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `comment` | string | No | Optional comment describing the purpose of the update. | | `layerKey` | string | Yes | The layer key identifying the specific layer to update. | | `projectKey` | string | Yes | The project key identifying the LaunchDarkly project containing the layer. Use LIST_PROJECTS to discover available project keys. | | `instructions` | array | Yes | Array of semantic patch instructions to apply to the layer. Each instruction specifies a modification to perform. Common instructions: updateName (updates the layer name), updateDescription (updates the layer description), updateExperimentReservation (modifies experiment reservations), removeExperiment (removes an experiment from the layer). | | `environmentKey` | string | No | The environment key for making environment-specific updates. For example, updating the reservation of an experiment. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Phase Status **Slug:** `LAUNCH_DARKLY_UPDATE_PHASE_STATUS` Tool to update the execution status of a phase in a feature flag release. Use when you need to start, complete, or pause a release phase in LaunchDarkly. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("active" | "completed" | "paused") | No | Valid phase status values for release phases. | | `flag_key` | string | Yes | The unique key of the feature flag associated with the release. | | `phase_id` | string | Yes | The unique identifier of the release phase to update. | | `audiences` | array | No | Extra configuration for audiences required upon phase initialization. Specify audience configurations when starting a phase. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project containing the flag. Use 'List Projects' action to find available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Release Pipeline **Slug:** `LAUNCH_DARKLY_UPDATE_RELEASE_PIPELINE` Tool to update an existing release pipeline in LaunchDarkly. Use when you need to modify pipeline configuration, phases, or metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | The name of the release pipeline. | | `tags` | array | No | A list of tags for this release pipeline. | | `phases` | array | Yes | An ordered list of release pipeline phases. Each phase is a logical grouping of one or more environments that share attributes for rolling out changes. | | `description` | string | No | A description of the release pipeline. | | `project_key` | string | Yes | The unique key identifying the LaunchDarkly project. Use 'List Projects' action to find available project keys. | | `pipeline_key` | string | Yes | The unique key of the release pipeline to update. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Release Policies Order **Slug:** `LAUNCH_DARKLY_UPDATE_RELEASE_POLICIES_ORDER` Tool to update the order of existing release policies for a project. Use when you need to change the priority order in which release policies are applied. The first policy in the list has the highest priority. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `policy_keys` | array | Yes | Ordered list of release policy keys. The order in this array determines the priority order of the policies, with the first item having the highest priority. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Release Policy **Slug:** `LAUNCH_DARKLY_UPDATE_RELEASE_POLICY` Tool to update an existing release policy for a specified project. Use when you need to modify release automation policies for progressive or guarded rollouts. Requires beta API version header. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | A human-friendly name for the release policy. | | `scope` | object | No | Target environments and flag tags for a release policy. | | `policy_key` | string | Yes | The human-readable key of the release policy to update. | | `project_key` | string | Yes | The project key identifying the project. Use LIST_PROJECTS action to discover available project keys. | | `releaseMethod` | string ("guarded-release" | "progressive-release") | Yes | The release method for this policy: 'guarded-release' monitors metrics during rollout, 'progressive-release' follows staged rollout without metric monitoring. | | `guardedReleaseConfig` | object | No | Configuration for guarded release policies. | | `progressiveReleaseConfig` | object | No | Configuration for progressive release policies. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update Audit Log Subscription **Slug:** `LAUNCH_DARKLY_UPDATE_SUBSCRIPTION` Tool to update an audit log subscription configuration using JSON Patch operations. Use when you need to modify subscription settings like name, configuration, enable/disable status, tags, or policy statements. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique identifier (ID) of the audit log subscription to update. This ID is returned when creating a subscription or can be found by listing subscriptions for an integration. | | `integration_key` | string | Yes | The integration key identifying the type of audit log subscription (e.g., 'datadog', 'msteams', 'splunk'). This key determines which integration service the subscription belongs to. | | `patch_operations` | array | Yes | An array of JSON Patch operations to apply to the subscription. Each operation modifies a specific field. Common paths include: '/name' (subscription name), '/on' (enable/disable), '/config' (configuration settings), '/tags' (array of tags), '/statements' (policy statements). | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Upsert Branch in Code Reference Repository **Slug:** `LAUNCH_DARKLY_UPSERT_BRANCH` Tool to upsert (create or update) a branch in a LaunchDarkly code reference repository. Use this to sync branch information including HEAD commit, sync time, and flag references. If the branch exists it will be updated, otherwise it will be created. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `head` | string | Yes | An ID representing the branch HEAD. For example, a commit SHA. | | `name` | string | Yes | The branch name. | | `repo` | string | Yes | The repository name. This is the name of the code reference repository configured in LaunchDarkly. | | `branch` | string | Yes | The URL-encoded branch name. For branch names with special characters, ensure they are properly URL-encoded. | | `syncTime` | integer | Yes | Unix timestamp in milliseconds when the branch is being synced. Use the current time when syncing. | | `commitTime` | integer | No | Unix timestamp in milliseconds when the commit was made. | | `references` | array | No | An array of flag references found on the branch. Each reference includes the file path and code hunks containing flag keys. | | `updateSequenceId` | integer | No | An optional ID used to prevent older data from overwriting newer data. If no sequence ID is included, the newly submitted data will always be saved. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not |