Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Update

channel_update

Updates a channel's name, active status, publishing and comment handling, or type-specific settings and credentials; only supplied fields change.

Instructions

Change a channel: its name, whether it is active, publishing and comment handling of a social account, or the settings and credentials of its type. Only what is given changes. Turning publishingEnabled on makes the channel a target for post_schedule. A new login of a connected account is channel_connect with the channelId.

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>",
      "channelId": "<channelId>"
    },
    "name": "channel_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name of the channel.
emailSslNoEMAIL: connect with SSL/TLS.
activatedNofalse pauses the channel: nothing is fetched or sent.
channelIdYesThe channel id (see channel_list).
emailHostNoEMAIL: mail server host name, e.g. mail.example.com.
emailPortNoEMAIL: SMTP port, e.g. 465 or 587.
commentModeNoSocial accounts: which comments on posts become conversations. ALL, QUESTIONS (emoji-only and off-topic comments are closed quietly) or NONE.
telegramChatNoTELEGRAM: the Telegram channel the bot posts to (@name, a t.me link or the id); the bot has to be an administrator of it. Optional: without it the channel only receives messages to the bot.
webchatColorNoWEBCHAT: accent color as hex, e.g. #2563eb.
webchatThemeNoWEBCHAT: widget theme.
webchatTitleNoWEBCHAT: title shown in the widget.
appstoreAppIdNoAPPSTORE: the app's Apple ID (the number in its App Store link).
appstoreKeyIdNoAPPSTORE: key id of the App Store Connect API key.
emailPasswordNoEMAIL: the mailbox password. Stored encrypted, never returned.
emailPortImapNoEMAIL: IMAP port, e.g. 993.
emailUsernameNoEMAIL: the mailbox address, which is also the login.
emailSignatureNoEMAIL: signature added to replies (HTML).
organizationIdYesThe organization id. Use organization_list to find it.
appstoreAppNameNoAPPSTORE: the app's name.
webchatPositionNoWEBCHAT: side of the page the launcher sits on.
appstoreIssuerIdNoAPPSTORE: issuer id of the App Store Connect API key.
commentAutoReplyNoSocial accounts: send AI replies to comments right away instead of keeping them as drafts.
telegramBotTokenNoTELEGRAM: the token of the bot from @BotFather. Stored encrypted.
publishingEnabledNoSocial accounts: let posts be published to this channel (post_schedule). Counts against the plan's publishing limit; the channel has to be allowed to publish (publishingAuthorized, see channel_connect).
appstorePrivateKeyNoAPPSTORE: content of the .p8 private key file. Stored encrypted.
blueskyAppPasswordNoBLUESKY: an app password (Bluesky settings, Privacy and security, App passwords), never the account password. Stored encrypted.
playstorePackageNameNoPLAYSTORE: the app's package name, e.g. com.example.app. The organization's service account (channel_playstore_service_account) has to be invited in the Play Console first.
webchatLauncherLabelNoWEBCHAT: text next to the launcher button.
webchatAllowedDomainsNoWEBCHAT: comma-separated domains the widget may be embedded on. Empty allows every site.
webchatRequireContactNoWEBCHAT: ask visitors for name and email before they can write.
webchatWelcomeMessageNoWEBCHAT: first message visitors see.
playstoreApplicationNameNoPLAYSTORE: the app's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly=false, destructive=false) but the description adds real value: patch semantics ("Only what is given changes"), the plan publishing-limit consequence of enabling publishing, and the prerequisite that the channel be publishingAuthorized. Not covered: failure behavior for bad credentials or partial updates.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the verb and scope, with no filler. The field enumeration in the first sentence is somewhat compressed but each clause carries information an agent needs.

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?

For a 32-parameter mutation with no output schema, the description covers the highest-risk aspects: partial-update semantics, secret handling referenced through type-specific credentials, publishing side effects, and the sibling boundary. A note on error/validation behavior or the response shape would close the remaining gap.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds grouping semantics beyond the schema by indicating that the applicable fields depend on the channel's type ("the settings and credentials of its type") and by tying publishingEnabled to post_schedule. It still does not say whether unknown/irrelevant type fields cause errors.

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 ("Change a channel") and enumerates the dimensions it can change: name, active flag, publishing/comment handling, and type-specific settings and credentials. It also explicitly names a sibling (channel_connect) for the adjacent operation, so an agent can distinguish it without opening schemas.

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?

Gives explicit routing away from channel_connect ("A new login of a connected account is channel_connect with the channelId") and states the precondition/side effect for publishingEnabled. It does not distinguish itself from channel_create or channel_get, so the when-to-use picture is clear but not exhaustive.

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