Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel List

channel_list
Read-onlyIdempotent

List an organization's support channels with their type, name, and health, including which social accounts allow publishing via post_schedule.

Instructions

List the channels of an organization: email, website chat, WhatsApp, Facebook Page (MESSENGER), Instagram, LinkedIn, Threads, X, TikTok, YouTube, Google Business Profile, Bluesky, Mastodon, Telegram, Google Play and App Store, with their type, name and health. publishingEnabled marks the social accounts posts can be published to (see post_schedule).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>"
    },
    "name": "channel_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety needs no restating. The description adds real value beyond them by describing what comes back (type, name, health) and explaining the semantics of the publishingEnabled flag, which annotations cannot convey.

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?

It is a single front-loaded sentence with no filler, but the 16-item platform enumeration consumes most of the length for marginal benefit — an agent mostly needs to know it returns all channels of the org with their type, name and health.

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?

There is no output schema and no nested parameters, so the description must carry return-value meaning, and it does: the returned attributes and the publishingEnabled semantics are both explained. Only the enumeration could be trimmed, and no critical detail for invoking the tool is missing.

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?

With one parameter at 100% schema coverage, the schema already documents organizationId and even routes to organization_list, so the description adds nothing new about the argument. Baseline 3 applies since structured data carries the parameter burden.

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 and resource ("List the channels of an organization") and scopes the result by enumerating the supported channel types plus the returned fields (type, name, health). It is clearly a collection read rather than the single-item channel_get, though the distinction is implied rather than stated.

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?

Implied usage is present: the note that publishingEnabled marks accounts posts can be published to, with a pointer to post_schedule, tells an agent one concrete reason to call it. There is no explicit when-not guidance or statement of alternatives such as channel_get, and the organization_list hint lives in the schema rather than the description.

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

Deploy Server

Other Tools