Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_workspace_members

Read-onlyIdempotent

Retrieve all members in a workspace with roles, status, and timestamps. Use the results to find a user_id for updating, fetching, or removing a workspace member.

Instructions

List every member in a workspace with organization role, workspace role, status, and timestamps. Use this to find a user_id before get_workspace_member, update_workspace_member, or remove_workspace_member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoFilter by workspace role
emailNoFilter by member email
page_sizeNoNumber of members per page
current_pageNoZero-based page number
workspace_idYesThe workspace ID to list members for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.2
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed4 schema fields changedv0.11.5
    • addedInput schema / properties / current_page
      Added value: +{
+  "description": "Zero-based page number",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / email
      Added value: +{
+  "description": "Filter by member email",
+  "format": "email",
+  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+  "type": "string"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Number of members per page",
+  "exclusiveMinimum": 0,
+  "maximum": 100,
+  "type": "integer"
+}
    • addedInput schema / properties / role
      Added value: +{
+  "description": "Filter by workspace role",
+  "enum": [
+    "admin",
+    "manager",
+    "member"
+  ],
+  "type": "string"
+}
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description's list of returned fields is largely redundant with the existing output schema, and it says nothing about pagination behavior despite page_size/current_page parameters. With annotations carrying the load, this is an adequate-but-thin contribution.

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

Conciseness5/5

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

Two sentences, zero filler, with the purpose statement front-loaded ahead of the usage routing. Every clause earns its place.

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

Completeness5/5

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

For a paginated read-only list tool with full schema coverage, complete annotations, and an output schema, the description supplies purpose, scope, and downstream usage. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so all five parameters (including the role enum, email pattern, and page bounds) are already documented in the schema. The description adds no filtering or pagination semantics beyond what the schema provides, which is the baseline-3 case.

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?

States a specific verb ('List') and resource ('every member in a workspace') and enumerates the scope of returned attributes (organization role, workspace role, status, timestamps). An agent can distinguish it from the many user/workspace siblings without opening the schema.

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

Usage Guidelines5/5

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

Explicitly names the workflow: use this to find a user_id before get_workspace_member, update_workspace_member, or remove_workspace_member. This routes the agent to the correct downstream tools and is exactly the kind of conditional guidance that prevents wrong-tool selection.

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