Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

schedule_weekly_posts

Plan and create weekly social media content schedules for art supply stores. Automatically organize posts by date, set posting frequency, and feature specific products to maintain consistent online presence.

Instructions

Create a weekly posting schedule with varied content types. Saves hours of planning time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusProductsNoComma-separated products to feature this week
postsPerDayYesNumber of posts per day (1-3 recommended)
startDateYesWeek start date (YYYY-MM-DD)

Implementation Reference

  • Handler implementation for the schedule_weekly_posts tool. Generates a 7-day social media posting schedule with randomized post types, times, and featured products. Returns formatted schedule text with suggestions for further tool usage.
    case 'schedule_weekly_posts': {
      const startDate = String(args?.startDate || '');
      const postsPerDay = Number(args?.postsPerDay || 1);
      const focusProducts = String(args?.focusProducts || '');
      
      const products = focusProducts ? focusProducts.split(',').map(p => p.trim()) : ['Acrylic Paint', 'Brushes', 'Canvas'];
      const postTypes = ['product_feature', 'behind_the_scenes', 'customer_spotlight', 'tip_of_the_day', 'promotion'];
      
      const schedule = [];
      const start = new Date(startDate);
      
      for (let day = 0; day < 7; day++) {
        const currentDate = new Date(start);
        currentDate.setDate(start.getDate() + day);
        const dateStr = currentDate.toISOString().split('T')[0];
        const dayName = currentDate.toLocaleDateString('en-US', { weekday: 'long' });
        
        for (let post = 0; post < postsPerDay; post++) {
          const postType = postTypes[Math.floor(Math.random() * postTypes.length)];
          const product = products[Math.floor(Math.random() * products.length)];
          
          schedule.push({
            date: dateStr,
            day: dayName,
            time: post === 0 ? '10:00 AM' : post === 1 ? '2:00 PM' : '6:00 PM',
            type: postType,
            suggestion: `${postType.replace('_', ' ').toUpperCase()}: Feature ${product}`
          });
        }
      }
    
      return {
        content: [{
          type: 'text',
          text: `šŸ“… Weekly Posting Schedule\nšŸ“ Week of ${startDate}\n\n${schedule.map(s =>
            `${s.day}, ${s.date} @ ${s.time}\n  ${s.suggestion}`
          ).join('\n\n')}\n\nšŸ’” Use 'generate_post_ideas' for specific content, then 'post_to_social_media' to publish!`
        }]
      };
    }
  • Tool schema definition including name, description, and inputSchema for validation. Part of the tools array registered with the MCP server.
    {
      name: 'schedule_weekly_posts',
      description: 'Create a weekly posting schedule with varied content types. Saves hours of planning time.',
      inputSchema: {
        type: 'object',
        properties: {
          startDate: { type: 'string', description: 'Week start date (YYYY-MM-DD)' },
          postsPerDay: { type: 'number', description: 'Number of posts per day (1-3 recommended)' },
          focusProducts: { type: 'string', description: 'Comma-separated products to feature this week' },
        },
        required: ['startDate', 'postsPerDay'],
      },
    },
  • src/index.ts:516-518 (registration)
    Registration of all tools including schedule_weekly_posts via the ListToolsRequestSchema handler, which returns the complete tools array containing the tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Saves hours of planning time' as a benefit but does not describe what the tool actually does (e.g., generates a schedule, saves it to a database, outputs a plan) or any behavioral traits like permissions, side effects, or output format. This leaves the agent with insufficient information to understand the tool's behavior beyond the basic purpose.

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 concise and front-loaded, with two sentences that directly state the purpose and benefit. There is no wasted language or redundancy. However, it could be slightly improved by integrating the benefit more seamlessly, but it remains efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a scheduling tool with no annotations and no output schema, the description is incomplete. It lacks details on what the tool outputs (e.g., a schedule object, a file, a confirmation), how it interacts with other systems, or any behavioral context. This makes it inadequate for an agent to fully understand the tool's operation and results.

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?

The input schema has 100% description coverage, so the schema already documents all parameters ('focusProducts', 'postsPerDay', 'startDate'). The description does not add any meaning beyond what the schema provides (e.g., it does not explain how 'varied content types' relate to parameters). With high schema coverage, the baseline score of 3 is appropriate, as the description adds no extra parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Create a weekly posting schedule with varied content types.' It specifies the verb ('Create') and resource ('weekly posting schedule'), and mentions a benefit ('Saves hours of planning time'). However, it does not explicitly differentiate from sibling tools like 'generate_post_ideas' or 'post_to_social_media', which reduces the score from a perfect 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions a benefit ('Saves hours of planning time') but does not specify contexts, prerequisites, or exclusions. With many sibling tools related to social media and content (e.g., 'generate_post_ideas', 'post_to_social_media'), the lack of differentiation is a significant gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wspotter/mcpart'

If you have feedback or need assistance with the MCP directory API, please join our Discord server