Skip to main content
Glama

Metadata MCP Connector

List User Accounts

list_user_accounts
Read-only

List accounts the current user has access to, with optional name filtering.

                            USE FOR: "which accounts do I have access to?", "show me my accounts", "what accounts can I manage?", "what is my account ID?", "which account am I logged into?", "what role do I have?", "show me account named X", "do you have an account called X?"

                            AUTH METHODS: JWT tokens (OAuth) | PAT tokens (prefix "pat-")

                            ARGS:
                            - name (optional for regular users, REQUIRED for super users unless `account_id` is given): partial account name to search for. Super users span the whole platform and would otherwise return an unbounded list, so a search term is mandatory for them. If a super user calls this with neither `name` nor `account_id`, the tool returns an error asking for one — re-call with the user's intended search term.
                            - account_id (optional): exact account id to look up. Use this instead of `name` when the search term is a number ("account 4368", "switch to 12057"), since account names are not ids and a numeric name search finds nothing. It satisfies the super-user search requirement on its own; supplying both narrows to accounts matching BOTH.

                            RESPONSE FORMAT (identical for JWT and PAT — the token format does not change the result):
                            Regular users: user_id, email, default_account_id, is_super_user, token_type, accounts[{account_id, name, role}]
                            Super users with neither argument: error response — supply `name` or `account_id` and retry.
                            Super users with name: matching accounts platform-wide (paged at 20).
                            Super users with account_id: the single matching account, or an empty list when no account carries that id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPartial account name to search for. Optional for regular users (acts as a filter); required for super users unless `account_id` is given (acts as the search query against the whole platform).
account_idNoExact account id to look up. Use instead of `name` when the search term is numeric; it satisfies the super-user search requirement on its own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description documents auth token types, the super-user mandatory search-term rule, the exact error path when neither name nor account_id is supplied, response shape variants, and 20-item paging. This is extensive behavioral disclosure that an agent cannot get from annotations alone.

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?

The description is structured into USE FOR, AUTH METHODS, ARGS, and RESPONSE FORMAT sections with a front-loaded one-sentence summary. Despite its length, every block conveys non-obvious information and there is no filler.

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?

Because there is no output schema, the description supplies the full response object shapes for regular users, super-user errors, name searches, and account_id searches, along with auth and argument requirements. Nothing an agent needs to decide when or how to call the tool is missing.

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

Parameters5/5

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

Although the schema already documents both parameters well, the description adds material meaning: why the super-user search is required, why numeric name searches fail, that supplying both parameters narrows with AND semantics, and the re-call-on-error behavior. These details significantly improve correct invocation beyond the schema.

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 opening sentence names the specific operation (list) and resource (accounts the current user has access to), plus optional name filtering. The USE FOR examples also pin down account ID, role, and login-state queries, making the tool's purpose unmistakable and distinct from detail-fetch or impersonation siblings.

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?

The USE FOR block provides explicit natural-language triggers such as 'which accounts do I have access to?' and 'what is my account ID?', which makes when-to-use very clear. However, it does not name alternatives or exclusions, such as using get_account_details for a single account's full details, so it stops short of full when-not-to-use 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.

Resources