list_admin_usersRetrieves paginated lists of admin users from Mealie, with options to filter, sort, and control results per page. Helps administrators audit user access and manage permissions.
Get All
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | ||
| paginationSeed | No | ||
| accept-language | No | ||
| orderByNullPosition | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, and 'Get All' discloses essentially nothing. It does not mention whether results are paginated, whether all admin users are returned at once, what filtering or ordering is supported, or any access requirements. It provides no meaningful behavioral context beyond the name.
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?
The description is extremely short, but this is under-specification rather than effective conciseness. 'Get All' is a fragment that omits the resource, any context, and any behavioral caveats. It does not fulfill the role of a useful tool description.
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?
Given the 8-parameter schema, zero annotations, and a large roster of sibling tools, the description is far too incomplete. The output schema helps with return values, but nothing explains the meaning of the pagination/filtering parameters, when this list should be used, or what admin-user listing entails. The definition is not viable for correct tool selection and invocation.
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 0% across 8 parameters, so the description must compensate, but 'Get All' explains none of them. Parameters like page, perPage, queryFilter, orderBy, and orderDirection are entirely undocumented in both the schema and the description. This is a complete failure to add semantic value.
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?
The description 'Get All' is vague and does not explicitly name the resource ('admin users'), though the tool name and title make the intent inferable. It lacks a clear verb+resource structure on its own and does not distinguish from sibling tools like get_admin_users_by_item or list_admin_about.
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?
No guidance is provided on when to use this tool versus alternatives. There is no mention of the pagination parameters, admin authorization context, or differences from related tools such as create_admin_users or get_admin_users_by_item. The description leaves all usage decisions to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.