Mark

List Channels

list_channels

Read-onlyIdempotent

Lists every social channel Mark publishes to (LinkedIn, Instagram, Facebook, X, TikTok, Pinterest, YouTube): whether an account is connected and which one, plus the channel's approval mode, approver role, active flag, posting time (24-hour HH:MM in the workspace timezone: when its first post on a slotted day goes out, each further post 3 hours later), and posting slots (each a weekday and a count of posts that day, with its slot id), and appUrl: the channel's page in Mark, where people set its slots and rules. How often a channel posts is its posting slots (update_posting_slots); its posting time is set with update_channel_settings. rulesSaved is false when the channel runs on Mark's default rules because none were saved. This is where to check whether a social account such as a LinkedIn page is connected. list_connections shows integrations instead, where all social accounts share one Social publishing row. Optional timezone (IANA) is checked and otherwise unused: slots have no time of their own. Does not change anything. For which Pinterest board new pins go to, call list_pinterest_boards. Related: get_connect_link, update_channel_settings, update_posting_slots, get_channel_rules, list_pinterest_boards.

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	Default
`timezone`	No	IANA zone, kept for older callers. Slots have no time of their own, so nothing renders in it.

Output Schema

Name	Required	Description	Default
`appUrl`	Yes
`channels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / timezone / description

Previous value: -"IANA zone to render slot times in. Does not change stored data. Defaults to the workspace timezone."New value: +"IANA zone, kept for older callers. Slots have no time of their own, so nothing renders in it."

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA zone to render slot times in. Does not change stored data. Defaults to the workspace timezone.",
+  "type": "string"
+}

First observedOct 1, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces with 'Does not change anything.' It adds genuine non-schema context: the semantics of rulesSaved defaults, how posting time relates to slots (first post plus 3-hour stagger), and the fact the timezone parameter is validated but otherwise inert. That said, with a full output schema present, the long return-field enumeration is largely redundant with structured data, so it lands at adequate-not-exceptional.

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?

Front-loaded with the core purpose and faultlessly information-dense, but the middle section is a single sprawling sentence stacking approval mode, approver role, active flag, posting time arithmetic, slot ids, and appUrl. Every fact is useful; the packaging could be tighter.

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?

For a zero-required-parameter read tool with a fully described one-param schema and an output schema, the description covers invocation context, sibling routing, return-field meaning, and the one confusing parameter. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and the schema itself explains the timezone field, so the baseline is 3. The description goes slightly further by clarifying that the timezone is 'checked' (validated) and otherwise unused because slots carry no time of their own, which resolves the obvious confusion an agent would have about a seemingly meaningful timezone argument.

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?

Opens with a specific verb and resource ('Lists every social channel Mark publishes to') and even enumerates the networks covered. It explicitly distinguishes itself from list_connections ('shows integrations instead') and list_pinterest_boards, so an agent can route correctly without opening a 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?

States the primary use case verbatim ('This is where to check whether a social account such as a LinkedIn page is connected') and names the alternatives with the condition that selects them, including a 'Related:' list of follow-up tools. Exclusion guidance is explicit rather than implied.

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

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