Mark

Update Channel Settings

update_channel_settings

Destructive

Updates a channel's settings, including approval mode and posting time. postingTime (24-hour HH:MM, workspace timezone, default 09:00) is when the channel's first post on a slotted day goes out; each further post that day goes 3 hours later. Which days it posts, and how many posts each day, are its posting slots: use update_posting_slots. approval=required keeps human review; approval=auto skips human review and can publish as soon as a post is submitted — only use auto when the workspace has chosen to skip review for that channel. approverRole=approver means admins only: only workspace admins can approve, request changes on, or reject that channel's posts, and only admins can change approverRole. Related: list_channels, get_channel_rules, submit_post.

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": {
      "channel": "<channel>"
    },
    "name": "update_channel_settings"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Notes for this channel, such as tone or format to keep. Mark's agent follows them, and get_drafting_guide shows them to AI assistants drafting for the channel.
`active`	No	false retires the channel.
`icpFit`	No	Whether this channel fits the ICP: confirmed or uncertain.
`channel`	Yes	Channel id, e.g. linkedin.
`approval`	No	required keeps review; auto skips human review.
`postingTime`	No	When the first post on a slotted day goes out, 24-hour HH:MM in the workspace timezone.
`approverRole`	No	member: any member can decide; approver: only workspace admins.
`bioDestination`	No	URL the profile bio link should open, e.g. https://example.com/offer.

Output Schema

Name	Required	Description	Default
`appUrl`	Yes
`channel`	Yes
`approval`	Yes
`postingTime`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / notes / description

Previous value: -"Internal notes for this channel."New value: +"Notes for this channel, such as tone or format to keep. Mark's agent follows them, and get_drafting_guide shows them to AI assistants drafting for the channel."

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / channel / enum

Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "pinterest",
-  "tiktok",
-  "x",
-  "linkedin",
-  "linkedin_article",
-  "blog",
-  "faq",
-  "competitor_page",
-  "landing_page",
-  "email",
-  "meta_ads",
-  "google_ads"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "pinterest",
+  "tiktok",
+  "x",
+  "linkedin",
+  "linkedin_article",
+  "blog",
+  "faq",
+  "competitor_page",
+  "meta_ads",
+  "google_ads"
+]

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / postingTime

Added value: +{
+  "description": "When the first post on a slotted day goes out, 24-hour HH:MM in the workspace timezone.",
+  "pattern": "^\\d{2}:\\d{2}$",
+  "type": "string"
+}

addedOutput schema / properties / postingTime
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / channel / enum

Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "pinterest",
-  "tiktok",
-  "x",
-  "linkedin",
-  "blog",
-  "faq",
-  "competitor_page",
-  "landing_page",
-  "email",
-  "meta_ads",
-  "google_ads"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "pinterest",
+  "tiktok",
+  "x",
+  "linkedin",
+  "linkedin_article",
+  "blog",
+  "faq",
+  "competitor_page",
+  "landing_page",
+  "email",
+  "meta_ads",
+  "google_ads"
+]

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / approverRole / description

Previous value: -"Who can approve posts on this channel: member or approver."New value: +"member: any member can decide; approver: only workspace admins."

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond annotations, the description explains that approval=auto skips human review and can publish as soon as a post is submitted, and that approverRole=approver restricts decisions and role changes to workspace admins. It does not restate the destructiveHint or non-idempotent behavior, but those are already covered by annotations and the remaining behavioral context is substantial.

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

Conciseness5/5

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

The description is front-loaded with the action and then uses dense, purposeful sentences to explain the non-obvious scheduling and approval semantics. Every sentence adds operational meaning, and the related-tools note is compact.

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 an 8-parameter mutation tool with annotations and an output schema, the description supplies the key behavioral constraints, sibling routing, and permission semantics an agent needs. Return values do not need explanation because an output schema exists.

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, but the description adds meaningful semantics for postingTime cadence, approval mode, and approverRole permissions beyond what the schema alone provides. It does not add much for notes, active, icpFit, or bioDestination, but those are already well documented in the schema.

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?

The description names the specific resource and action: updating a channel's settings, including approval mode and posting time. It also distinguishes this from update_posting_slots by explicitly routing slot changes there, so an agent can differentiate it from the closest sibling.

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?

It gives explicit when-to-use and when-not-to-use guidance: posting days and counts belong to update_posting_slots, and approval=auto should only be used when the workspace has chosen to skip review for that channel. It also states the admin-only constraint around approverRole, leaving little inference for tool selection.

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?