Keytomic

Start content calendar

start_content_calendar

Starts a content calendar run for a site, the same as Generate in the Calendar. Without confirm, returns the plan of a run started now and starts nothing (status plan): the automation days, the first and last day (UTC, to the end of the billing cycle), the topic count, whether the run starts the article of today’s topic, and the calendar runs left. Show the plan to the user, and call again with confirm: true only after the user agrees. With confirm: true, reads the plan again and starts the run (status started) with a runId: follow it with get_content_calendar_progress. The run uses 1 of the site’s calendar runs for this billing cycle, researches keywords with DataForSEO and plans the topics with AI; when it plans a topic today, it starts that article, which uses 1 article. When the site cannot start a run now, both calls answer a tool error and use nothing. When the plan allows more than one run in a billing cycle, a later run adds topics and removes none, so one day can get two topics; the daily automation writes one topic a day. The site needs saved Image Studio settings, a reviewed brand profile and at least one automation day.

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>"
    },
    "name": "start_content_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	true starts the run. Send it only after the user saw the plan this tool returns without confirm and agreed. Without it, the tool returns the plan and starts nothing.
`projectId`	Yes	Site to act on, from list_sites.

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 (non-read-only, non-idempotent, non-destructive) it discloses the real costs: one calendar run from the billing cycle, plus one article if today's topic is planned. It explains failure semantics ('both calls answer a tool error and use nothing') and the additive effect of extra runs, which annotations cannot convey.

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?

Front-loaded with the action and the plan/confirm protocol, and every sentence carries operational weight (costs, errors, prerequisites). It is dense and slightly repetitive against the confirm schema text, but not padded.

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 mutating, non-idempotent, costly tool with no output schema, the description still covers the return shape (status plan vs started, runId, plan fields), the follow-up tool, resource consumption, edge cases (two topics in one day), and prerequisites. Nothing an agent needs to call it safely is missing.

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% and the schema already documents confirm's purpose in detail, so the description mostly restates it. The added value comes from tying confirm to the user-agreement workflow rather than the parameter itself.

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?

Opens with a specific verb and resource ('Starts a content calendar run for a site') and anchors it to a known UI action ('the same as Generate in the Calendar'). It also names the follow-up sibling get_content_calendar_progress, so the agent can place it in a workflow without reading other schemas.

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

Usage Guidelines5/5

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

Gives an explicit two-step protocol: call without confirm to get a plan, show it to the user, then call again with confirm: true only after agreement. It also states preconditions (saved Image Studio settings, reviewed brand profile, at least one automation day) and when the tool errors out.

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

All Keytomic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?