360dialog

List channels

list_channels

Read-only

Find a channel by passing in an identifier.

A channel is a phone number. By calling this tool you retrieve information about the phone number/channel in 360Dialog.

Results are paginated; use the 'page' and 'size' arguments to page through results if there are more than fit in a single page.

Returns: If not found, returns "Not found". If found, returns information of channels, like WABA ID, client ID, channel ID, and app ID, along with the current page, total pages, and total count.

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

Input Schema

Name	Required	Description
`page`	No	Page number to retrieve, starting at 1.
`size`	No	Number of channels to return per page.
`filter`	No	Optional filter. You can pass a phone number, client ID, or channel ID here. Defaults to None; call without this argument if you want to get all channels.

Output Schema

Name	Required	Description	Default
`page`	No
`found`	Yes
`message`	No
`channels`	No
`total_count`	No
`total_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond them: pagination semantics and the distinctive "Not found" return string for a missing channel. The enumeration of returned fields (WABA ID, client ID, channel ID, app ID) is largely redundant with the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening domain explanation is valuable and front-loaded, but the "Returns:" block duplicates what the output schema already carries and the middle paragraph restates pagination twice. Tightening to two sentences (what a channel is, and how to scope/paginate) would lose nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, annotations, and an output schema, most burdens are lifted. However, the description never resolves the find-vs-list ambiguity or its relationship to `get_channel_profile`, which is the main thing an agent needs to select correctly among 100+ siblings.

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 the schema already explains `page`, `size`, and that `filter` accepts a phone number, client ID, or channel ID. The description only restates pagination at a high level and says "identifier" without adding the specificity the schema already provides. Baseline 3 is appropriate.

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

Purpose3/5

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

The description does explain the domain ("A channel is a phone number") and says it retrieves channel information from 360Dialog, but the lead sentence "Find a channel by passing in an identifier" frames a lookup tool while the tool name/title and optional `filter` indicate a list tool that returns all channels when unfiltered. It also fails to distinguish itself from the sibling `get_channel_profile`, which an agent would reasonably consider for single-channel retrieval.

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: pass an identifier to find a specific channel, and use `page`/`size` to page through results. There is no explicit statement of when to prefer this over `get_channel_profile` or how it relates to `list_users`/`get_self`, and no note that omitting `filter` returns everything (that only appears in the schema).

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

All 360dialog 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?