Skip to main content
Glama
Sign In
apparelhub-mcp

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_account_members

Read-only

Retrieve account members and their per-workspace assignments for agency or Enterprise accounts. Filter by role, workspace, or search term; paginated and read-only; requires an account-wide key.

Instructions

List account members and their per-workspace assignments (agency / Enterprise). Filterable + paginated. Needs an account-wide key. Read-only.

[#b3bd65]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_account_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text match on email/username.
pageNoPage number (default 1).
per_pageNoPage size (default 50, max 100).
account_roleNoFilter by account role.
in_workspaceNoOnly members assigned to this workspace uuid.
workspace_roleNoMembers holding this workspace role (combine with in_workspace for "role in that workspace").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so 'Read-only' is redundant. However, the description adds genuinely useful behavioral context beyond the annotations: the account-wide key authentication requirement and that results are paginated. Return shape and total counts are still unspecified.

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?

Front-loaded and tight — purpose, scope, filtering/pagination, auth need, and safety all in two short sentences. The trailing '[#b3bd65]' artifact is meaningless noise that slightly detracts.

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?

For a 6-parameter list tool with no output schema but full schema coverage and read-only annotations, the definition covers the essentials (scope, filters, pagination, auth). It would be complete with a note on what pagination metadata is returned or how it relates to sibling member tools.

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

Parameters3/5

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

Schema coverage is 100%, so all six parameters (query, page, per_page, role filters) are already documented in the schema. The description only summarizes them as 'Filterable + paginated' without adding syntax or combining rules beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (list) and resource (account members) plus the extra value proposition (per-workspace assignments) and the plan scope (agency/Enterprise). It is clearly distinguishable from most siblings, but does not explicitly contrast with near-neighbors like list_invites or get_account_overview.

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 through 'Filterable + paginated' and a prerequisite ('Needs an account-wide key'), but never states when to choose this over alternatives such as list_invites, assign_workspace_member, or get_account_overview. The context is inferable but not spelled out.

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

Deploy Server

Other Tools