Botsify

List bot messenger users

list-bot-messenger-users

Read-onlyIdempotent

List messenger users for the selected bot via POST /v1/get-bot-users with limit and skip.

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-bot-messenger-users"
  }
}

Input Schema

Name	Required	Description	Default
`skip`	No	Number of users to skip for pagination
`limit`	No	Maximum users to return. Default 100.

Output Schema

Name	Required	Description	Default
`result`	Yes	JSON or plain text body returned by the Botsify HTTP API

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds the POST endpoint and pagination details, but does not disclose behavioral nuances like the requirement for a prior bot selection or any rate limits. It does not contradict annotations.

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 a single concise sentence that front-loads the main purpose and includes the endpoint and key parameters. Every word earns its place with no fluff or redundancy.

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?

Given the annotations, output schema, and simple parameter list, the description is fairly complete. It could be improved by explicitly noting the prerequisite of selecting a bot and differentiating from the similar 'list-messenger-users' tool, but it is adequate for the tool's complexity.

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?

The schema description coverage is 100%, so the baseline is 3. The description only mentions 'limit and skip' without adding extra meaning beyond the schema, which already describes both parameters with defaults.

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 description clearly states a specific verb ('List') and resource ('messenger users for the selected bot'). It also distinguishes from the sibling 'list-messenger-users' by scoping to a selected bot, and mentions the HTTP endpoint and pagination parameters.

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 description implies usage for a selected bot and includes the endpoint, but it does not explicitly state when to use this tool over the similar sibling 'list-messenger-users'. There is no exclusion or alternative guidance, though the context is reasonably clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Botsify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?