Skip to main content
Glama

B2B Creators

by com.b2b-creators.mcp
OverviewDiscussionsAdmin

Choose extra channels for a post

set_post_channels

Set which connected Facebook/Instagram channels (from list_channels) an existing post also goes out to alongside LinkedIn, when it is published or scheduled. Replaces the post's previous unpublished channel list; pass an empty list for LinkedIn only. Instagram needs media, max 2200 chars and 30 hashtags. On a draft this only attaches the channels; on a scheduled post the schedule is paused until the user re-confirms. SAFETY: this never publishes or schedules by itself. It returns status 'awaiting_confirmation' and a confirmation link; nothing goes live until the user opens the link and ticks each account (all unticked by default). Always tell the user to open the link and tick the accounts. Never treat 'all accounts' as a blanket instruction — list every account you requested by name so the user can check them. You cannot confirm on the user's behalf.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoOptional link for Facebook text posts.
post_idYesPost id from list_scheduled_posts.
channel_idsYesChannel ids from list_channels.
text_overridesNoOptional per-channel copy: { channel_id: text }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / link
      Added value: +{
+  "description": "Optional link for Facebook text posts.",
+  "format": "uri",
+  "type": "string"
+}
    • addedInput schema / properties / text_overrides
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Optional per-channel copy: { channel_id: text }.",
+  "type": "object"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld/idempotent/destructive hints; the description adds critical behavior: replaces previous unpublished channel list, pauses scheduled posts until re-confirmation, returns 'awaiting_confirmation' with a link, and all accounts are unticked by default. It also discloses that confirmation cannot be done on the user's behalf, which is exactly the kind of context annotations do not provide.

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?

Front-loaded with the core action, then organized into replacement behavior, constraints, draft/scheduled differences, and safety. The safety instructions are repeated in slightly different forms but each sentence adds operational guidance for the agent, so the length is justified.

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 complex tool with no output schema, the description is remarkably complete: it covers prerequisites, return status, confirmation flow, account ticking defaults, and the draft/scheduled distinction. Nothing an agent needs to decide whether and how 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.

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description adds meaningful parameter behavior: passing an empty channel_ids list means LinkedIn only, and Instagram requires media, max 2200 chars, and 30 hashtags. It doesn't elaborate on text_overrides or link, but the schema already documents those.

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 ('Set') and resource ('which connected Facebook/Instagram channels an existing post also goes out to'), with source of IDs, and distinguishes from publish/schedule by clarifying it only sets channels on an existing post. The title 'Choose extra channels for a post' aligns, and the description makes the tool's role unmistakable.

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?

Provides clear context: use for existing posts, with channel ids from list_channels, and explains draft vs scheduled behavior. Does not explicitly name alternatives like publish_to_channels or when not to use it, but the safety line ('never publishes or schedules by itself') gives enough guidance.

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

All B2B Creators toolsInspect
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