Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

list_project_memberships

Retrieve the list of members and their designations for a given Amazon DataZone project within a domain. Supports pagination and sorting.

Instructions

Lists the memberships of a specified Amazon DataZone project within a domain.

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

project_identifier (str): The identifier of the project whose memberships you want to list.
    Pattern: ^[a-zA-Z0-9_-]{1,36}$
    Required: Yes

max_results (int, optional): The maximum number of memberships to return in a single call (1–50).

next_token (str, optional): A token for pagination. Use this token from a previous response to retrieve the next set of memberships.
    Length: 1–8192 characters

sort_by (str, optional): The attribute by which to sort the memberships.
    Valid Values: "NAME"

sort_order (str, optional): The sort order for the results.
    Valid Values: "ASCENDING" | "DESCENDING"

Returns: dict: A dictionary containing: - members (List[dict]): A list of project members, where each member includes: - designation (str): The role or designation of the member within the project. - memberDetails (dict): Additional details about the member (structure depends on implementation).

    - nextToken (str, optional): A token to retrieve the next page of results if more memberships exist.
        Length: 1–8192 characters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_byNo
next_tokenNo
sort_orderNo
max_resultsNo
domain_identifierYes
project_identifierYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes pagination, sorting, and the return structure (members list, next token). It does not mention authentication or error conditions, but for a read operation it is fairly transparent.

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, but somewhat verbose as it repeats schema details. However, since the schema lacks descriptions, this is justified.

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?

Given no output schema, the description details the return structure and pagination. It covers the main aspects, though it could mention prerequisites like existing domain/project.

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%, but the description fully documents each parameter with patterns, valid values, and defaults. It adds significant meaning beyond the schema's bare titles and types.

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

Purpose5/5

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

The description clearly states the tool lists memberships of a specified Amazon DataZone project, with the verb 'lists' and resource 'memberships'. It distinguishes from siblings like create_project_membership (creation) and list_projects (projects list).

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?

No explicit guidance on when to use this tool versus alternatives like search or list_projects. Usage is implied by the tool's purpose, but no when-to-use or when-not-to-use conditions are stated.

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