BlogSEO

Get hosted blog status

get_hosted_blog_status

Idempotent

Re-checks the hosted blog's DNS and certificate like the Refresh status button and returns the current status (Waiting for DNS propagation, Issuing SSL certificate, Ownership verification needed, DNS misconfigured, CAA blocked, Connected...), the DNS records still to add (the CNAME plus any TXT ownership record), the last error and the detected DNS provider with a link to its settings. Poll it every few minutes after adding the record; DNS changes take 5 to 60 minutes. Limited to 30 checks per hour. Free. Pass website_id when the account has several websites (see get_account).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`website_id`	No	Website id from get_account. Optional when the account has a single website.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes
`blog_url`	Yes
`hostname`	Yes	Subdomain serving the blog.
`config_id`	Yes
`next_step`	Yes	What to do next for the current status: records to add, DNS and SSL wait times, or the article URL pattern once connected.
`registrar`	Yes
`created_at`	Yes
`last_error`	Yes
`updated_at`	Yes
`website_id`	Yes
`dns_records`	Yes	Records still to add at the DNS provider.
`is_connected`	Yes	true once DNS resolves and the certificate is issued.
`status_label`	Yes
`dashboard_url`	Yes
`dns_verified_at`	Yes
`registrar_warning`	Yes	Instruction specific to the detected DNS provider to follow when adding the records; null when none applies.
`ssl_provisioned_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedOutput schema / properties / next_step

Added value: +{
+  "description": "What to do next for the current status: records to add, DNS and SSL wait times, or the article URL pattern once connected.",
+  "type": "string"
+}

addedOutput schema / properties / registrar_warning

Added value: +{
+  "description": "Instruction specific to the detected DNS provider to follow when adding the records; null when none applies.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "config_id",
-  "website_id",
-  "hostname",
-  "blog_url",
-  "status",
-  "status_label",
-  "is_connected",
-  "dns_records",
-  "last_error",
-  "registrar",
-  "dns_verified_at",
-  "ssl_provisioned_at",
-  "created_at",
-  "updated_at",
-  "dashboard_url"
-]New value: +[
+  "config_id",
+  "website_id",
+  "hostname",
+  "blog_url",
+  "status",
+  "status_label",
+  "is_connected",
+  "dns_records",
+  "last_error",
+  "registrar",
+  "dns_verified_at",
+  "ssl_provisioned_at",
+  "created_at",
+  "updated_at",
+  "dashboard_url",
+  "registrar_warning",
+  "next_step"
+]

First observedSep 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond annotations: it triggers a re-check like the Refresh status button (explaining why readOnlyHint is false despite being a 'get'), enforces a 30-checks-per-hour rate limit, is free, and has a 5-60 minute propagation window. This is exactly the side-effect, quota, and timing disclosure an agent needs.

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 paragraph is front-loaded with the action and its result, then layers operational details (timing, rate limit, param guidance). It is dense and largely earns its length, though the long parenthetical status list borders on redundant given the output schema.

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?

A complete picture for a single-optional-param status tool: it covers behavior, timing, limits, and cost, and an output schema handles return-value structure. Only auth/permission prerequisites are unstated, a minor gap.

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 routing guidance not present in the schema: pass website_id when the account has several websites and consult get_account to obtain it. That meaningfully improves correct invocation.

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?

States a specific verb+resource (re-check the hosted blog's DNS and certificate) and precisely enumerates what it returns, including concrete status strings. An agent can distinguish it from create_hosted_blog or get_website_setup_guide without opening any 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?

Gives explicit operational guidance: poll every few minutes after adding the record, DNS changes take 5-60 minutes, and pass website_id when the account has multiple sites (pointing to get_account). It lacks an explicit 'when not to use' or named alternative for checking status, keeping it just short of a 5.

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

All BlogSEO 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.