Skip to main content
Glama
MelMayssonOwen

TimeToPost MCP server

One-click AutoSEO onboarding (auto-configure)

autoseo_auto_configure

Automate AutoSEO onboarding for a connected site: generate topic proposals, apply safe default settings, and optionally create a pending draft for human approval.

Instructions

ONE-CLICK AutoSEO onboarding — "auto do the thing". For a connected site (siteId from autoseo_connect_site / autoseo_list_sites), this single call replaces the manual autoseo_propose_topics → autoseo_configure sequence: it (a) runs the topic-proposal engine to derive question-shaped topics/pillars for the site, (b) saves them into the site config with safe defaults for anything the user has not already set — weekly cadence, "illustration" image style, and approvalMode "draft" (the human approval gate; auto-configure NEVER opts a user into unattended publishing) — and (c) if generateFirst is true, also queues the first article on the top proposed topic as a PENDING draft awaiting human approval (counts against the plan's monthly article quota; omit it to configure without generating). Existing deliberate settings are preserved: user-typed pillars stay first with proposed topics appended (deduped), and an existing cadence/imageStyle/approvalMode is never overwritten. Returns { config, proposedTopics (question + rationale, relay these to the user), firstPost? ({ status: "queued", draftId } on success — approve it with approve_draft after the human reviews it) }. Prefer this right after autoseo_connect_site when the user just wants it set up; use autoseo_propose_topics + autoseo_configure instead when they want to hand-pick topics. CAPABILITY: draft — creates content that cannot reach an audience on its own. Safe for a draft-only agent token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite id from autoseo_connect_site / autoseo_list_sites
generateFirstNoAlso queue the first article (top proposed topic) as a pending draft behind the human approval gate. Uses one article of the monthly quota.
Behavior5/5

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

Annotations are minimal (no hints), but the description extensively discloses behavior: it never overwrites existing settings, preserves user-typed pillars, enforces approvalMode 'draft', never opts into unattended publishing, affects monthly quota, and returns a specific structure. It also states the CAPABILITY 'draft' and safety for draft-only agent tokens, adding important context beyond the schema.

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 long and somewhat run-on, but every sentence conveys useful information for a complex tool. It is front-loaded with the main purpose and clearly organized via parentheticals. Slightly verbose but justified by the tool's complexity.

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?

Given no output schema, the description explains the return value in detail (config, proposedTopics, firstPost). It covers preconditions (connected site), side effects (quota, approval), and safety/limits. For a 2-param tool, this is highly complete.

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 covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds nuance: generateFirst queues a draft behind human approval and uses quota; omitting it configures without generating. It also clarifies siteId source. This adds marginal meaning beyond schema.

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 clearly states the tool's function: one-click AutoSEO onboarding that combines topic proposal and configuration. It explicitly contrasts with the manual sequence (autoseo_propose_topics → autoseo_configure) and names sibling tools, making its purpose and scope unambiguous.

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?

Explicit usage guidance is provided: 'Prefer this right after autoseo_connect_site when the user just wants it set up; use autoseo_propose_topics + autoseo_configure instead when they want to hand-pick topics.' This clearly states when to use and when not, naming the alternative.

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/MelMayssonOwen/timetopost-mcp'

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