JuzPost

List channel groups

list_groups

Read-onlyIdempotent

Lists channel groups (named sets of accounts) with their member account ids. Use this when the user names a group ("post to my brand accounts") to resolve it to the account ids schedule_post takes. Returns groups[] (id, name, accountIds, accountCount), nextCursor and hasMore. Does NOT create or edit groups.

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_groups"
  }
}

Input Schema

Name	Required	Description
`name`	No	Filter by exact group name.
`sort`	No	createdAt (default) or name.
`limit`	No	Page size, 1–100.
`cursor`	No	Opaque cursor from the previous page. Omit for the first page.

Output Schema

Name	Required	Description
`groups`	Yes
`hasMore`	Yes
`nextCursor`	Yes	Pass as `cursor` to fetch the next page; null when there is none.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds the negative scope boundary (no create/edit) and names the return fields (groups[], nextCursor, hasMore), which gives useful behavioral context, though the output schema also carries the return shape.

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?

Three tight sentences: definition, usage trigger with the downstream consumer, then a scope exclusion. Front-loaded and every clause carries information; 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?

Covers what the tool returns, when to call it, which sibling consumes the result, and what it does not do, which is everything an agent needs for a read-only list tool with a full schema, annotations, and an output schema.

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 description coverage is 100%, so name, sort, limit, and cursor are fully documented in the schema including defaults, bounds, and enum values. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource (lists channel groups) and immediately defines the domain concept as 'named sets of accounts' with their member account ids. An agent can distinguish this from list_accounts, list_workspaces, and list_posts without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ('when the user names a group ... to resolve it to the account ids schedule_post takes') that names the sibling tool consuming the output, plus an explicit when-not ('Does NOT create or edit groups'). Nothing about selection is left to inference.

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

All JuzPost 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?