Skip to main content
Glama

freedom-mcp

by com.getfreedomos
OverviewDiscussionsAdmin

Submit content to pipeline

submit_content_to_pipeline
Destructive

Submit manual content to a pipeline for transformation. Use when user says "add this to my changelog", "create a newsletter from this", "transform this content", "make social posts", "post to LinkedIn/Facebook/X", "give this to my team", or provides content to be processed — first clear ask, this turn; the approval queue is the yes (do not re-ask). Content will be transformed using the pipeline's persona and ICPs unless as_final_draft=true (operator already wrote the post — queue it as-is for Approve). Social pipelines publish to the pipeline's declared destination (x/linkedin/instagram/facebook/threads — set via update_pipeline; undeclared defaults to x) after human approval; instagram items REQUIRE media_artifact_ids.

[write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time. Call it on the first clear ask; the card is the yes — do not re-ask in chat.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesRaw content to transform (updates, notes, announcements, etc.)
companyIdYesFreedomOS company id to act within (you must be a member). Required for company-scoped tools.
pipeline_idYesID of the pipeline to submit to (get from list_pipelines)
as_final_draftNoWhen true, this IS the post — queue it for human Approve without running the persona transform (Alex). Use for operator-curated copy, especially sourced faith. Auto-queue stays off for held grains. Default false.
media_artifact_idsNoOptional. Artifact IDs (image or video, from generate_image_xai / generate_video, same company) to attach as media on this post. Required for visual social posts — the post publishes with this media attached. Each ID must belong to this company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_final_draft
      Added value: +{
+  "description": "When true, this IS the post — queue it for human Approve without running the persona transform (Alex). Use for operator-curated copy, especially sourced faith. Auto-queue stays off for held grains. Default false.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the sparse annotations, it discloses substantial side effects: content is transformed using the pipeline's persona and ICPs, social pipelines publish only after human approval, Instagram items require media_artifact_ids, and first use may require manager approval with from-now-on versus just-once semantics. This is rich behavioral context not captured in the structured fields. There is no contradiction with readOnlyHint=false or destructiveHint=true.

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?

The description is front-loaded with the core purpose and usage triggers, and its length is largely justified by the complex approval and publishing behavior. Minor redundancy costs it a point: 'the approval queue is the yes (do not re-ask)' is restated later as 'the card is the yes — do not re-ask in chat.'

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 side-effecting tool with no output schema, the description covers the complete workflow: when to call, what transformation happens, the as_final_draft bypass, social destination defaults, Instagram media requirements, and the manager-approval wrinkle. The only slight gap is not naming sibling exclusions, but the trigger and workflow detail is enough to make the tool safely and correctly invokable.

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?

The schema already covers all five parameters, so the baseline is 3. The description adds meaningful extra semantics for as_final_draft (queue operator-written copy as-is) and media_artifact_ids (Instagram requires them), and it ties pipeline destination defaults to update_pipeline. It does not add much for content or companyId, but the schema already handles those clearly.

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 opening sentence names a specific action and resource: submitting manual content into a pipeline for transformation. It enumerates concrete user triggers like 'add this to my changelog' and 'make social posts', and the 'manual content' wording helps separate it from ingest-style siblings. An agent can tell what this tool does and when to reach for it.

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?

The description gives explicit trigger phrases and instructs the agent to call it on the 'first clear ask' rather than re-asking, which is strong selection guidance. It also differentiates the as_final_draft path for already-written posts and references update_pipeline for social destinations. However, it does not explicitly name when-not-to-use or compare against near siblings like post_to_x or publish_pipeline_item.

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

All freedom-mcp 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