Skip to main content
Glama

ADS Beast

list_clients

Read-only

Return the clients of this organization with their budgets, status and connected advertising accounts. A long list comes back as a page {result, total, has_more, next_offset}.

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
limitNoClients per page.
offsetNoClients to skip; use next_offset from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new information: the response envelope shape {result, total, has_more, next_offset} and what fields each client record carries. That is real added context, especially since no output schema exists.

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?

Two sentences, zero waste, with the resource/scope statement front-loaded and the pagination note following it. Nothing to trim.

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?

For a two-optional-parameter list tool with no output schema, the definition covers scope, returned fields, and the pagination envelope — the pieces an agent needs to call and consume it correctly. Annotations handle the safety story.

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

Parameters3/5

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

Schema coverage is 100%, so limit and offset are already documented, including the note to reuse next_offset. The description reinforces the paging concept but adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Return') and resource ('clients of this organization') and enumerates the payload contents (budgets, status, connected advertising accounts), which lets an agent tell it apart from the many list_* siblings by resource alone. It stops short of naming an alternative, but the resource noun is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: paging behavior is mentioned, so the agent can infer this is the enumerate-all-clients call, but there is no explicit when-to-use, when-not-to-use, or pointer to a filtered/alternative listing tool.

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.