Skip to main content
Glama

Visibility Genies

List clients

list_clients
Read-only

Lists the clients the user's workspace groups its sites (projects) under: each client's id and name, and its sites by name and id. Free: buys no data. Pass a client's id to create_project as clientId to add a site under it, or to set_project_client to move a site into it. When the user belongs to several organizations, each client is labeled with its organization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
metaNo
clientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds a genuinely new behavioral fact not in annotations: 'Free: buys no data', i.e. no credit consumption. It also notes multi-org labeling behavior, though it says nothing about pagination or result limits.

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?

Three sentences, front-loaded with what is returned, then downstream uses, then the multi-org edge case. Dense but readable; 'Free: buys no data' is terse to the point of being cryptic about what 'data' means.

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?

An output schema exists, so the description need not explain return values, yet it does so briefly anyway. With zero parameters and full annotation coverage, almost nothing an agent needs is missing; only pagination or ordering expectations for a list tool are unaddressed.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It still clarifies how the returned client id is consumed elsewhere (as clientId), which is useful connective tissue.

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 (lists) and a precisely scoped resource (the clients a workspace groups its sites under), and enumerates what comes back: client id and name, plus sites by name and id. That framing distinguishes it from list_projects without needing the sibling's schema.

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 concrete downstream routing: pass a client id to create_project as clientId to add a site, or to set_project_client to move a site into it. It does not state when to prefer list_projects over this tool, so the exclusion side is absent.

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