Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

list_environment_profiles

List environment profiles in Amazon DataZone domains, filtered by AWS account, region, blueprint, or project, for targeted environment discovery.

Instructions

Lists environment profiles within a specified Amazon DataZone domain, optionally filtered by AWS account, region, blueprint, and project.

Args: domain_identifier (str): The identifier of the Amazon DataZone domain. Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ Required: Yes

aws_account_id (str, optional): The AWS account ID to filter results.
    Pattern: r"^\d{12}$"

aws_account_region (str, optional): The AWS region to filter results.
    Pattern: ^[a-z]{2}-[a-z]{4,10}-\d$

environment_blueprint_identifier (str, optional): The identifier of the blueprint used to create the environment profiles.
    Pattern: ^[a-zA-Z0-9_-]{1,36}$

max_results (int, optional): Maximum number of results to return (1–50).

name (str, optional): Filter environment profiles by name.
    Length: 1–64 characters
    Pattern: ^[\w -]+$

next_token (str, optional): A pagination token returned from a previous call to retrieve the next set of results.
    Length: 1–8192 characters

project_identifier (str, optional): The identifier of the Amazon DataZone project.
    Pattern: ^[a-zA-Z0-9_-]{1,36}$

Returns: dict: A dictionary containing: - items (List[dict]): A list of environment profile summaries. Each item includes: - awsAccountId (str): AWS account where the profile exists. - awsAccountRegion (str): AWS region of the profile. - createdAt (str): Timestamp when the profile was created. - createdBy (str): Identifier of the user who created the profile. - description (str): Description of the profile. - domainId (str): The domain associated with the profile. - environmentBlueprintId (str): ID of the blueprint used. - id (str): Unique ID of the environment profile. - name (str): Name of the environment profile. - projectId (str): ID of the associated project. - updatedAt (str): Timestamp of last update.

    - nextToken (str): Token for retrieving the next page of results, if any.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
next_tokenNo
max_resultsNo
aws_account_idNo
domain_identifierYes
aws_account_regionNo
project_identifierNo
environment_blueprint_identifierNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses pagination via next_token and max_results, and return structure with items and nextToken. No annotation provided, but description adds value by detailing fields in the response. However, does not explicitly state read-only nature or authorization requirements.

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

Conciseness4/5

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

Well-structured with Args and Returns sections; front-loaded purpose. Some verbosity in parameter docs but each part adds value. Appropriate for complexity.

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

Completeness4/5

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

Covers purpose, parameters, and return structure thoroughly. Missing error handling or authorization details, but acceptable for a list operation with straightforward behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation including patterns, required status, and constraints. This adds significant meaning beyond the bare schema.

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

Purpose4/5

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

Description clearly lists environment profiles with filtering options, using specific verb 'list' and resource 'environment profiles'. It distinguishes from sibling tools by focusing on a specific entity, but does not explicitly differentiate from similar list tools like list_environments.

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

Usage Guidelines3/5

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

Implies usage when needing environment profiles for a domain, optionally filtered. No explicit guidance on when not to use or alternatives among sibling list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/awslabs/amazon-datazone-mcp-server'

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