Skip to main content
Glama

Search users, groups and placeholder users

search_principals
Read-onlyIdempotent

Find users, groups, and placeholder users and retrieve their IDs for assignments, watchers, time entries, and memberships. Resolve names to numeric IDs before using any principal parameter.

Instructions

Find users, groups and placeholder users, and get their ids.

This is the id-producing tool for every principal parameter in this server: assignee/responsible on work packages, watcher ids, the user_id of a time entry, and principal_id for create_membership. Names are never accepted where an id is wanted — resolve here first, and never guess a numeric id.

Use it to answer "who is Grace Hopper's account", "which groups exist", "who is a member of the demo project". Returns the standard list envelope: items of {id, name, type, email?, login?, status?} plus pagination{total,page,page_size,has_more} and notes.

Pitfalls. email, login and status are only returned for user principals the authenticated account may see — a null email means "not visible to you", not "no email". Group principals can hold memberships and be assigned work, so filter by type when you specifically need a person. Matching is substring-based, so a short query matches broadly; prefer the full name or the login. member_of_project filters by membership, not by whether the person ever touched the project.

Cross-references: get_user for one user's full detail; list_memberships for who holds which roles in a project; create_membership to grant access; list_roles for the role ids that grant needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
typeNoRestrict to one kind of principal. 'user' = people who log in, 'group' = user groups (assignable and grantable as a unit), 'placeholder' = licence-free stand-ins. Omit to search all three.
queryNoFree text matched against name, login and email (substring, case-insensitive). Omit it to page through every visible principal.
statusNoRestrict to an account status. 'active' is the usual filter when looking for someone to assign work to; 'locked' accounts keep old assignments but take no new ones. Groups and placeholder users have no status and are excluded when this is set.
page_sizeNoPrincipals per page, 1-100.
member_of_projectNoOnly principals who are members of this project. Numeric project id or the URL identifier; an identifier costs one extra lookup. Use it before assigning work — a user who is not a member usually cannot be assigned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sumsNoPresent only when show_sums was requested.
itemsNoThe page of results.
notesNoDegradation markers: capped aggregations, unavailable modules, …
groupsNoPresent only when group_by was requested.
paginationYesTotal/page/page_size/has_more.
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses non-obvious behavior: email/login/status are only returned for visible users ('a null email means not visible to you, not no email'), group principals are assignable, matching is substring-based and broad, and member_of_project filters by membership rather than activity. These are valuable behavioral nuances not captured in annotations.

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?

The description is longer than typical but well-organized into purpose, usage, pitfalls, and cross-references. Every sentence earns its place; there is no filler. The 'Pitfalls' section is particularly high-density. Could be slightly tightened, but structure aids scannability.

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?

With no required parameters, an output schema for return envelope, and full schema coverage, the description still adds critical context: id resolution workflow, visibility semantics, and relationship to other tools. It is complete for an AI agent to select and invoke confidently, covering all decision-relevant aspects.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds meaningful guidance over the schema: explains that type='group' includes assignable groups, warns about short queries matching broadly, and clarifies member_of_project usage ('Use it before assigning work — a user who is not a member usually cannot be assigned'). This elevates it above baseline, though not all params get equal attention.

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 opens with 'Find users, groups and placeholder users, and get their ids', a specific verb+resource+result statement. It explicitly positions itself as 'the id-producing tool for every principal parameter in this server', distinguishing it from sibling tools like get_user, list_memberships, and create_membership.

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?

Provides explicit when-to-use and when-not-to-use guidance: 'Names are never accepted where an id is wanted — resolve here first, and never guess a numeric id'. It also gives example queries ('who is Grace Hopper's account', 'which groups exist') and names alternatives: 'get_user for one user's full detail; list_memberships for who holds which roles; create_membership to grant access; list_roles for role ids'.

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/kar-thik/openproject-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server