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, active flag, and recurring posting slots (weekday, local time, UTC instant, slot id, workspace timezone), 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). 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) renders slot times in that zone; it does not change stored data. 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`timezone`	No	IANA zone to render slot times in. Does not change stored data. Defaults to the workspace timezone.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered; the description usefully reinforces this ('Does not change anything'). It adds genuine behavioral context beyond annotations: rulesSaved semantics (false = running on Mark's default rules) and that the timezone parameter only affects rendering, not stored data.

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-loads the core resource and its returned fields, then layers differentiation and routing. The parenthetical enumeration of slot fields (weekday, local time, UTC instant, slot id, workspace timezone) is somewhat verbose given an output schema exists, but overall the text is dense rather than padded.

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 read-only, single-optional-param list tool with both annotations and an output schema, the description covers everything needed: returned fields, special-case semantics (rulesSaved), parameter side-effect profile, and routing to related tools. Nothing an agent needs to call it correctly 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?

Schema coverage is 100% and the single timezone parameter is fully documented in the schema (IANA zone, no data mutation, defaults to workspace timezone). The description restates this rather than adding new syntax or edge cases, so the baseline 3 is appropriate.

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+resource ('Lists every social channel Mark publishes to') and immediately distinguishes itself from the closest sibling ('list_connections shows integrations instead'). An agent can tell what this returns and how it differs from the alternatives 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?

Explicitly names when to use it ('This is where to check whether a social account such as a LinkedIn page is connected'), names the alternative (list_connections), and routes to further siblings (list_pinterest_boards, get_connect_link, update_posting_slots). Nothing 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 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?