Skip to main content
Glama
Sign In
claw-mcp-toolkit

claw-mcp-toolkit

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

social_content_calendar

Plan and schedule social media posts for a week by generating content calendars tailored to specific niches and platforms.

Instructions

Generate a 7-day content calendar for social media

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "niche": "<niche>"
    },
    "name": "social_content_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheYesYour niche (e.g. 'AI agents', 'crypto', 'SaaS')
platformNoPlatformtwitter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Zero annotations provided, and description discloses no behavioral traits: it doesn't state whether this creates persistent records, returns a structured plan vs just ideas, requires authentication, or has side effects like API rate limit consumption.

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?

Single sentence, eight words, zero redundancy. Front-loaded action verb with specific qualifiers that earn their place. Perfect information density.

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?

Generating a multi-day content calendar is a complex operation with structured output. No output schema exists, and the description fails to compensate by describing the calendar format, structure, or what specific elements (post ideas, timing, hashtags) are returned.

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?

Schema has 100% coverage with basic descriptions, but the tool description adds crucial semantic context not in schema: the '7-day' temporal scope constraint. This informs the agent about the volume of content being generated beyond what the schema parameters suggest.

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?

Specific verb 'Generate' and resource '7-day content calendar' clearly define scope. The temporal scope ('7-day') distinguishes this from sibling tools like social_generate_tweet (single posts) and social_thread_builder (immediate threads), though it could explicitly contrast with these.

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?

No guidance on when to select this versus siblings like social_generate_tweet, social_thread_builder, or social_hashtag_research. Missing conditions like 'use when planning a week ahead vs posting immediately'.

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

Deploy Server

Other Tools