bulk_schedule_posts
Schedule multiple social media posts at once (up to 50 posts per batch). More efficient than scheduling posts individually.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| posts | Yes | Array of posts to schedule |
VibeMarketing
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses the batch size limit (up to 50), which is helpful, but does not mention what happens on partial failures, whether the operation is atomic, or any authentication/validation details. This leaves significant behavioral gaps for a bulk mutation tool.
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 two sentences, front-loaded with the primary action, and every word contributes value. It states the function, the batch limit, and the efficiency benefit without any fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the schema is rich and the description covers the core capability, there is no output schema and no mention of return values or error handling. For a bulk operation that can partially fail, the absence of information about partial success or response format leaves the description incomplete in a practical sense.
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 baseline is 3. The description adds no parameter-specific meaning beyond the schema, only restating the batch limit already present in maxItems. It does not clarify nuances like the relationship between posts or any conditional requirements.
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 clearly states the tool schedules multiple posts at once, differentiating it from the sibling 'schedule_post' which schedules individually. The specific verb 'schedule' and resource 'multiple social media posts' make the purpose unambiguous.
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 phrase 'up to 50 posts per batch' and 'more efficient than scheduling posts individually' gives clear context for when to use this tool over the singular scheduling option. However, it stops short of explicitly stating 'use schedule_post for a single post' or outlining exclusion criteria, so it earns a 4 rather than a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.