Skip to main content
Glama
MelMayssonOwen

TimeToPost MCP server

Connect a site to AutoSEO (start here)

autoseo_connect_site

Connect a new site to AutoSEO by selecting one of four connectors: hosted, WordPress REST, GitHub PR, or webhook. Returns site ID, token, and capabilities to start generating content.

Instructions

START HERE for AutoSEO on a new site. Connects ONE of the four connector kinds (intrusion ladder, least intrusive first) and returns { id, kind, publicToken, capabilities }. WHICH KIND + WHICH FIELDS: kind "hosted" is the ZERO-SETUP DEFAULT — needs ONLY name; TimeToPost hosts AND SSR-renders the blog itself (full SEO: JSON-LD, sitemap, robots AI-crawler allow-list) and the response includes hostedUrl ("your blog is live at ..."); nothing to install, works for ANY site — pick it when unsure. kind "wp_rest" connects a WordPress site over its own REST API — needs url (the WP site), username, and appPassword (created in WP Admin → Users → Profile → Application Passwords); no plugin, no code; connect runs the REAL capability probe, so a bad credential fails right here with the exact reason. kind "git_pr" commits article files (Markdown/MDX + frontmatter) to a GitHub repo and the user's own CI deploys them — needs token (a fine-grained PAT or GitHub App installation token with contents:write) and repo ("owner/name"), plus optional branch, contentDir, and mode ("pr" opens a reviewable pull request per article, the default; "direct" commits straight to the branch); connect verifies write access and auto-detects the SSG + content convention (returned as capabilities.detected — confirm contentDir with the user if ssg is "unknown"). kind "webhook" is the most-control path for ANY stack (Next.js, Rails, PHP, a serverless function): TimeToPost POSTs signed article payloads to endpointUrl, authenticated with an HMAC signingSecret — pass one or omit it to have the backend generate it; then call autoseo_integration_kit, install the /autoseo-publish endpoint into the user's codebase, and confirm with autoseo_verify_site. After ANY kind: autoseo_configure → autoseo_propose_topics / autoseo_generate_post. name is a human label shown in the TimeToPost dashboard. capabilities updates each time autoseo_verify_site re-probes the site; publicToken is only needed for autoseo_integration_kit's renderMode "ssr-hosted" (set it as that site's AUTOSEO_PUBLIC_TOKEN env var). CAPABILITY: draft — creates content that cannot reach an audience on its own. Safe for a draft-only agent token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoRequired for kind "wp_rest": the WordPress site URL (a bare domain is fine)
kindYesConnector kind: "hosted" (zero-setup default — only name needed, we host the blog), "wp_rest" (WordPress REST — url + username + appPassword), "git_pr" (GitHub repo — token + repo, optional branch/contentDir/mode), "webhook" (signed receiving endpoint — endpointUrl + optional signingSecret)
modeNogit_pr: "pr" (default) opens a pull request per article — a git-native approval gate; "direct" commits straight to the branch
nameYesHuman-readable label for this site, shown in the dashboard
repoNoRequired for kind "git_pr": the repository as "owner/name" (a github.com URL also works)
tokenNoRequired for kind "git_pr": a GitHub fine-grained PAT or App installation token with contents:write on the repo
branchNogit_pr: base branch for commits/PRs; omit to use the repo's default branch
usernameNoRequired for kind "wp_rest": the WP username the Application Password belongs to
contentDirNogit_pr: directory article files land in; omit to auto-detect from the repo (e.g. content/blog, _posts)
appPasswordNoRequired for kind "wp_rest": a WordPress Application Password (WP Admin → Users → Profile → Application Passwords)
endpointUrlNoRequired for kind "webhook": the URL TimeToPost will POST signed articles to (e.g. https://example.com/autoseo-publish)
signingSecretNowebhook: HMAC secret used to sign payloads; omit to let the backend generate one
Behavior5/5

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

The description discloses many behavioral traits beyond annotations: for wp_rest, 'connect runs the REAL capability probe, so a bad credential fails right here with the exact reason'; for git_pr, 'connect verifies write access and auto-detects the SSG + content convention'; and for webhook, the signing secret generation. It also notes the CAPABILITY: 'draft' and the safety implication. This is extensive and transparent.

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 but well-structured with logical sections: start, return, each connector kind, post-connect steps, and capability warning. It is dense and front-loaded with 'START HERE'. However, it is somewhat verbose; while every sentence carries meaning, the length could be slightly trimmed without losing information.

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 the tool's complexity (4 connector kinds, 12 params, no output schema), the description is remarkably complete. It explains the return value ({ id, kind, publicToken, capabilities }), side effects (e.g., probe for wp_rest, write-access verification for git_pr), and the overall workflow. It also covers edge cases like publicToken usage and capability restrictions. This is fully sufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds meaningful semantics by grouping parameters per kind and explaining defaults and requirements. For example, 'kind "hosted" is the ZERO-SETUP DEFAULT — needs ONLY name', and 'mode ... "pr" opens a reviewable pull request per article, the default'. It clarifies the exact meaning and combinations of parameters, going well beyond the 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 purpose: 'Connects ONE of the four connector kinds' and 'START HERE for AutoSEO on a new site.' It names the specific resource (site) and action (connect), and distinguishes itself from sibling tools by positioning as the entry point. The return object is also specified, making the tool's role 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?

The description explicitly states when to use this tool ('START HERE') and provides guidance for choosing among the four connector kinds, e.g., 'pick it when unsure' for hosted. It also directs follow-up steps: 'After ANY kind: autoseo_configure → autoseo_propose_topics / autoseo_generate_post.' This is a clear usage roadmap with alternatives.

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