Skip to main content
Glama

Create calendar topic

create_calendar_topic

Creates one topic in a site’s content calendar from a title, the same as Add topic in the Calendar with a title the user writes. AI picks the topic’s keywords, intent, outline and article type (blogType), Keytomic checks the keywords’ search volume with DataForSEO, and AI checks the topic against the site’s current topics and pages, unless allowCannibalization is true. A created topic uses 1 of the site’s monthly keyword searches (the keywordSearches section of get_project shows them). If the topic collides, nothing is created and the result lists the collisions (status collision): a collision found from the title alone uses no keyword search, and a collision found after AI picked the keywords uses 1. Show the collisions to the user, and if the user still wants the topic, call again with allowCannibalization true; a call on the same day does not use a second keyword search for this title. Creating a topic uses no articles: the daily automation writes the article on its scheduled day, and then it counts. But the site must have an article left this month, or an Article Credit. A repeated call creates the topic again. The site needs a content calendar run and saved Image Studio settings first. Returns the created topic; when the workspace cannot open it for now, returns lockedTopicCount instead.

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": {
      "projectId": "<projectId>",
      "title": "<title>"
    },
    "name": "create_calendar_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTopic title, which becomes the article title, such as "How to feed a sourdough starter". AI finds the topic’s keywords from it.
projectIdYesSite to act on, from list_sites.
scheduledDayNoScheduled day, YYYY-MM-DD, as the Calendar shows it (UTC). On this day the daily automation writes the article and, with automatic publishing on, publishes it. Pick tomorrow (UTC) or a later day: the automation writes each day’s article at 00:00 UTC and never goes back to a past day. Without it, or with null, the topic has no day, and the automation does not write the article until a day is set with update_calendar_topic.
authorProfileIdNoAuthor of this article, from the settings section of get_project. Without it, the site’s default author applies.
customInstructionsNoInstructions the writer follows for this article only, up to 1000 characters.
allowCannibalizationNotrue creates the topic even when it collides with current topics or pages. Send it only after the user saw the collisions and agreed.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses billing consequences (1 monthly keyword search, collision accounting), prerequisites, non-idempotent behavior ('a repeated call creates the topic again'), article-credit requirements, and what the return contains including lockedTopicCount. This is unusually rich behavioral context for a mutating tool.

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 definition is front-loaded with purpose and prerequisites, and nearly every sentence carries operational information about keyword-search accounting, collisions, or article credits. It is dense and somewhat repetitive around collision handling, but not padded with filler.

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?

For a complex six-parameter mutating tool with no output schema, the description covers prerequisites, side effects, collision outcomes, return values, and failure/locked cases. An agent has enough information to call it correctly and to interpret the result.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning around the title parameter by explaining that AI derives keywords from it and around allowCannibalization by tying it to the collision-review workflow. It does not further explain scheduledDay, authorProfileId, or customInstructions, leaving those to their already thorough schema descriptions.

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 states a specific verb and resource (creates one topic in a site's content calendar) and frames it against the manual Calendar action. It clearly distinguishes creation from later article generation and from updating a topic, so an agent can identify the tool's role without opening the schema.

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?

It gives explicit operational guidance: the site needs a content calendar run and saved Image Studio settings, collisions must be shown to the user before retrying with allowCannibalization, and a collision retry on the same day does not consume another keyword search. It stops short of naming sibling alternatives such as update_calendar_topic or add_keywords_to_calendar, so the routing guidance is strong but not exhaustive.

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