Skip to main content
Glama

List project members

list_project_members
Read-onlyIdempotent

List existing members of an accessible project. Use their IDs for task assignees. Does not invite anyone or expose email addresses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "list_project_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
limitNoMaximum number of items to return, from 1 to 100. Defaults to 50.
projectIdYesExisting accessible project ID returned by list_projects.

Output Schema

NameRequiredDescriptionDefault
itemsYesAccessible records on this page.
nextCursorYesPass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new facts beyond them: no invitations are sent, and email addresses are not exposed in results — useful for an agent reasoning about privacy and side effects but it stops there without covering pagination or result shape (though an output schema exists).

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?

Three short sentences, front-loaded with the core action, then the practical use, then the negative constraints. Every sentence adds information and none repeats the title or schema.

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?

Output schema and rich annotations already carry result shape and safety semantics, so the description only needs to add scope and caveats, which it does. The remaining gap is small: it doesn't hint at membership volume or pagination expectations, which a listing tool could reasonably mention.

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 projectId, limit and after are already fully documented with patterns and ranges. The description only adds that the project must be 'accessible' and that member IDs feed task assignees, which is marginal beyond the schema — 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 and resource ('List existing members of an accessible project') with an explicit accessibility scoping qualifier. It doesn't name a contrasting sibling (e.g. list_projects or list_tasks), so the agent must infer differentiation from the description alone.

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

Usage Guidelines4/5

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

Gives a concrete downstream use ('Use their IDs for task assignees') and an explicit exclusion ('Does not invite anyone'), which rules out a misuse case. No named alternative tool is offered for the related case of finding members another way, so it stops short of full when-vs-what guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.