Skip to main content
Glama

List clients

clipember_list_clients
Read-onlyIdempotent

Show the user's clients — groups of connected social accounts, one per brand or customer they manage — with each client's accounts (connectionId). To post for a client, pass those connectionIds as clipember_create_post targets; to see a client's posts, call clipember_list_scheduled_posts and keep the posts of those accounts.

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": "clipember_list_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds behavior the annotations do not: it discloses what the response contains (clients plus their accounts with connectionId) and how that output feeds other tools. Pagination or volume characteristics for a user with many clients are not mentioned.

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?

Front-loaded with the core action, then the concept definition, then follow-on guidance — a sensible order. The em-dash appositive is long and the second sentence is a compound two-clause run-on, but each sentence carries distinct information and nothing is pure 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?

There is no output schema, so the description carries the return-value burden and does it: it states that accounts and their connectionIds come back with each client, and tells the agent what to do with them. For a zero-parameter, read-only listing tool this is complete.

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 no parameters, so there is no parameter semantics for the description to explain; the baseline applies. The description correctly spends its words on output meaning and follow-on usage instead of inventing input detail.

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?

Uses a specific verb and resource ('Show the user's clients') and immediately defines the domain concept — 'groups of connected social accounts, one per brand or customer they manage' — which disambiguates it from the many other list_* siblings. It also names the key returned field (connectionId), so an agent knows exactly what this call yields.

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?

Explicitly routes the agent: use the returned connectionIds as targets for clipember_create_post, and use clipember_list_scheduled_posts to see a client's posts filtered by those accounts. That is clear downstream guidance with named alternatives; it lacks only an explicit statement of when this tool is a poor choice.

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