Skip to main content
Glama

جدولة نشر

create-content-schedule

Add a post to the content calendar: the video of a script, or a supporting post, image, carousel, story or text post, with or without a script. Name the script if the post belongs to one; without a script, give the post a title and, if the person says so, the project it belongs to. Say when it goes out, or save it as a draft with no date. For a carousel, the text of each slide goes in the slides, one entry per slide, in order, and never in the publishing notes. Media already online can be added as links here; to add media files from this computer, add the post first, then prepare the upload, run the commands, and confirm the upload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctaNoThe call to action.
kindNoWhat the post is: a main video, a short clip, an image, a carousel, a story, or a text post. A main video if left out.
titleNoThe post's own title. Needed when the post has no script; with a script, leave it out to use the script's title.
scriptNoاسم نص الذي يوضع هذا بداخله، كما هو مكتوب في برديّة.
slidesNoA carousel's slides: the text of each slide, one entry per slide, in order, at most 20 of up to 1000 characters each. Sending it replaces the whole list; leaving it out keeps the slides as they are. Only a carousel has slides.
statusNoWhere the post stands: a draft (an idea, with or without a date), scheduled, or published.
projectNoاسم مشروع الذي تريد ربطه، كما هو مكتوب في برديّة. إذا لم يطابق الاسم، أو طابق أكثر من واحد، يعود إليك سؤال بدل أن يُربط الخطأ.
hashtagsNoHashtags, as plain text.
platformsNoThe platforms this post goes out on, by the names the person uses for them. Left out, the platforms of its script are used, else the default platforms of its project, else the person's own default platforms.
script_idNoالرقم الذي جاءك من القائمة، إن كان لديك. وإن لم يكن، فاكتب الاسم بدل الرقم.
is_primaryNoWhether this is the episode itself: the one post that moves its script to scheduled or published. Only a main video or a short clip can be.
descriptionNoThe long description for the platform.
media_linksNoLinks to media already online, such as a YouTube or Drive link. Bardiyah keeps the links only. To add files from this computer, prepare and confirm an upload instead.
short_captionNoThe short caption that accompanies the post.
additional_notesNoAnything else the person publishing should know.
publish_datetimeNoWhen it goes out, the day and the time, written as 2026-09-01 18:00. A draft may have none.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Given that the annotations are minimal and generic, the description bears the full burden of behavioral disclosure. It provides crucial traits like the structure for carousel slides (one entry per slide) and the dependency on the `prepare-post-media-upload` process for file-based media.

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

Conciseness3/5

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

The tool is inherently complex, leading to a very long description. While well-structured and not repetitive, its length sacrifices ultimate conciseness, though the detailed categorization helps organization.

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?

The definition is extremely complete for this complexity. It covers all edge cases mentioned in the schema, from platform defaults to the specific process of adding computer files, ensuring an agent has all necessary context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Although schema coverage is 100%, the description adds high semantic value by explaining how parameters interact. For instance, it specifies that `is_primary` is restricted to 'main video' or 'short clip,' and that the `title` parameter is only needed when the post has no script.

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 immediately identifies its core function as adding a post to the content calendar, specifying the breadth of supported media types (video, image, carousel, text). It is highly specific and clearly defines its scope within the content management system.

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?

The description acts as a comprehensive functional guide, providing explicit rules for complex logic, such as when to use a script title versus a custom title. It also dictates clear operational procedures, such as how to handle media uploads (prepare/run/confirm) and when to save as a draft vs. schedule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources