Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

threads_channel_publish_post

Destructive

Publish a post to the connected Meta Threads account. Supports TEXT, IMAGE, VIDEO and CAROUSEL (2-20 items). Text is limited to 500 characters and 5 links. Media must be given as a PUBLIC URL — Threads has no file upload endpoint. Returns the published post id and permalink.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPost text. Required for TEXT, optional caption otherwise. Max 500 characters and 5 links.
alt_textNoAccessibility text for a single IMAGE or VIDEO post.
image_urlNoPublic URL of the image (JPEG/PNG, max 8MB). IMAGE only.
video_urlNoPublic URL of the video (MOV/MP4, max 1GB / 5 min). VIDEO only.
media_typeYesTEXT, IMAGE, VIDEO or CAROUSEL.
reply_to_idNoPublish as a reply to this Threads post/reply id.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
reply_controlNoWho may reply to this post. OMIT to leave it at the account's default (everyone).
carousel_itemsNoCAROUSEL only: 2-20 items, each {media_type: IMAGE|VIDEO, image_url|video_url, alt_text?}. Order is the render order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds real behavioral context beyond that: media must be PUBLIC URLs because Threads has no upload endpoint, plus text/char/limit constraints and the post-id/permalink return.

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?

Four short sentences, zero filler, and the core capability plus key constraint (public URL only) are front-loaded before the return-value note. Every sentence earns its place.

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 9-parameter publish tool with no output schema, the description covers media modes, key constraints, the URL requirement, and even the return shape (post id and permalink). Only the absence of routing guidance against siblings keeps it from being fully complete.

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 description coverage is 100%, so the schema already documents all nine parameters including the enum media_type and reply_control. The description's constraint mentions (500 chars, 5 links, carousel 2-20) largely restate what the schema already says, so baseline 3 applies.

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 precise verb+resource ('Publish a post to the connected Meta Threads account') and enumerates supported content modes (TEXT, IMAGE, VIDEO, CAROUSEL). An agent can immediately distinguish it from sibling mutation tools like threads_update and threads_delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful operational context (public URLs required, no file-upload endpoint) but never states when to choose this tool over alternatives such as threads_update or instagram_publish_media. Usage is implied by the resource, not routed.

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

All dialogbrain 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