Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Draft a content calendar

social-content_calendar-generate
Read-onlyIdempotent

Place supplied posts on a caller-supplied window. Dated posts stay on their date. Undated posts fill empty days in input order. No caption is written and nothing is scheduled. Price $0.05 USDC. POST /api/v1/social-content/calendar-generate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "social-content_calendar-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
postsNoposts, array. Optional.
windowNowindow, object. Optional.
accountNoaccount, object. Optional.
commentsNocomments, array. Optional.
hashtagsNohashtags, array. Optional.
platformNoplatform, string, length 0 to 40. Optional.

Output Schema

NameRequiredDescriptionDefault
slotsNoslots. Array.
statusNostatus. String.
scrapedNoscraped. Boolean.
findingsNofindings. Array.
unplacedNounplaced. Array.
checkedAtNocheckedAt. String.
publishedNopublished. Boolean.
scheduledNoscheduled. Boolean.
limitationsNolimitations. Array.
postsRemovedNopostsRemoved. Boolean.
reachInventedNoreachInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the price ($0.05 USDC), the x402 payment handshake, and that an unpaid call returns payment terms rather than executing — the single most important behavioral fact for this tool. The POST endpoint is also named, which is consistent with readOnlyHint because the description confirms nothing is persisted or scheduled. Return shape is left to the output schema.

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?

Four short sentences, front-loaded with the core behavior, then the placement rules, then the negative scope, then the commercial/transport facts. No filler and nothing repeated from the annotations.

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

Completeness4/5

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

For a zero-required-parameter tool with a rich output schema, the description covers what matters: the algorithm, the non-goals, the price and the payment gate. The one gap is that ten optional inputs are accepted with no indication of which ones actually affect the generated calendar versus being inert payload fields.

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 coverage is 100%, so the parameters are already documented at the field level and the baseline is 3. The description clarifies the semantics of the two load-bearing inputs (posts and window) — notably the dated/undated distinction and input-order fill — but says nothing about how csv, file, json, text, account, comments, hashtags or the engagement metrics interact with calendar generation.

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?

"Place supplied posts on a caller-supplied window" states a specific verb and resource, and the two follow-up sentences pin down the exact placement algorithm (dated stay, undated fill empty days in input order). It is unmistakably a calendar drafting tool, though it never references a sibling to sharpen the boundary against alternatives.

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 exclusions do real routing work: "No caption is written and nothing is scheduled" tells an agent to look elsewhere if it wants copywriting or publishing. What is missing is a positive statement of the precondition (you must already have posts) or a named alternative for the scheduling case.

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