Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

search_group_profiles

Search for group profiles in an Amazon DataZone domain by specifying group type and optional text to filter results. Supports paginated responses.

Instructions

Searches for group profiles within a specified Amazon DataZone domain.

This operation allows you to find groups by specifying a group type and optional search text. Pagination is supported through maxResults and nextToken.

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

group_type (str): The type of group to search for.
    Valid values:
        - "SSO_GROUP"
        - "DATAZONE_SSO_GROUP"
    Required: Yes

max_results (int, optional): The maximum number of results to return in a single call.
    Valid range: 1–50
    Required: No

next_token (str, optional): Pagination token from a previous response. Use this to retrieve the next set of results.
    Length: 1–8192 characters
    Required: No

search_text (str, optional): Free-text string used to filter group profiles.
    Max length: 1024
    Required: No

Returns: dict: A response object containing: - items (List[dict]): A list of group profile summaries. Each summary includes: - domainId (str): The domain to which the group belongs. - groupName (str): The name of the group. - id (str): The unique identifier of the group profile. - status (str): The current status of the group profile. - nextToken (str, optional): A token to retrieve the next page of results, if more are available. Length: 1–8192 characters

Raises: HTTPError: If the API request fails or returns an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_typeYes
next_tokenNo
max_resultsNo
search_textNo
domain_identifierYes
Behavior3/5

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

With no annotations, the description carries the burden. It discloses pagination behavior and error raising (HTTPError), but does not explicitly confirm read-only nature, rate limits, or side effects. The behavioral context is adequate but not comprehensive.

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

Conciseness4/5

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

The description is well-structured with clear sections (Args, Returns, Raises) and the main purpose is front-loaded. It is fairly concise but could be slightly tighter by removing redundant phrasing. Still, no wasted sentences.

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?

No output schema exists, so the description must explain return values—it does so with a structured dict including items and nextToken. Error handling is mentioned. However,it lacks edge case details or explanations of status codes. Overall complete for the complexity.

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?

Schema coverage is 0%, so the description fully documents parameters. It adds patterns (e.g., domain_identifier regex), valid values (group_type enum), ranges (max_results 1-50), lengths, and defaults, going well beyond the schema's type-only information.

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

Purpose5/5

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

The description explicitly states the tool searches for group profiles within an Amazon DataZone domain, specifying the resource (group profiles) and the action (search). It distinguishes from siblings like 'search_user_profiles' and generic 'search' by focusing on group profiles.

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?

The description implies usage by stating it allows finding groups with group type and search text, but it does not explicitly state when to use it versus alternatives or when not to use it. No exclusions are provided.

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