Retrieve Productboard workspace members, optionally filter by role, to view team access and assignments.
List Productboard workspace members. Optionally filter by role.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Filter by member role | |
| limit | No | Number of results (default 25, max 500) | |
| pageCursor | No | Pagination cursor from previous response |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not state that results are paginated, what the default page size is, whether this is a read-only safe call, or what permission level is required for listing members.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with the core action front-loaded and the optional refinement second. No wasted words or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple three-parameter list tool with full schema coverage and no output schema, the description is minimally sufficient. It leaves gaps around pagination behavior and how this tool relates to the singular get_member sibling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all three parameters (role, limit, pageCursor) are already documented in the schema, including the enum values and default. The description's mention of the role filter adds nothing beyond what the schema states, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List Productboard workspace members'), and the optional role filter narrows scope. It does not explicitly distinguish itself from the sibling get_member (singular) or get_member_activities, so sibling differentiation is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Optionally filter by role' hints at one usage path but gives no when-to-use guidance, no mention of pagination follow-up, and no routing advice against get_member or get_member_activities.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.