Skip to main content
Glama

Check Publish Status

get_publish_status
Read-only

Check whether the site is published and return its live URL and latest report: broken_links, dead_nav_links, incoherent_pages, checks, design_gate, live_verified and SEO coverage. report.checked:true means a report was produced; report.audit_ran:false means the link, form and design audit did not run for this deploy, so findings are unavailable. Do NOT describe a publish as clean unless the audit ran. Read the report and offer fixes for findings, including forms that submit into the void, buttons do nothing, and hand-rolled auth. If audit_ran is false, run seo_audit on production_url. status is one of: published, deploying, not_published, unknown_app. This is the current state; do not poll repeatedly.

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": {
      "app_id": "<app_id>",
      "context": "<context>"
    },
    "name": "get_publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app ID to check
contextYesWhy this call, in one short sentence. Used to improve the connector; never include credentials or personal data.

Output Schema

NameRequiredDescriptionDefault
nameNo
slugNo
app_idNo
reasonNo
reportNo
statusNo
production_urlNo
screenshot_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the meaning of report.checked and report.audit_ran, warns against describing a publish as clean when the audit did not run, and enumerates the allowed status values. It also states the no-polling expectation. This is exactly the operational context an agent needs before interpreting results.

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?

Key facts are front-loaded: what it returns, then how to interpret report flags, then the escalation path, then the status enum. It is a bit dense and mixes output interpretation with directives, but every sentence carries information and nothing is redundant.

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?

Although an output schema exists, the description supplies the interpretation layer the schema cannot: what checked/audit_ran mean, the status enum values, and what to do when the audit did not run. Combined with the safety annotations and full param coverage, an agent has everything needed to call and act on this tool.

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 description coverage is 100%, so app_id and context are already documented in the schema. The description adds no syntax, format, or constraint details about the parameters, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Check whether the site is published and return its live URL and latest report.' It then enumerates the exact report fields (broken_links, dead_nav_links, incoherent_pages, checks, design_gate, live_verified, SEO coverage), which distinguishes it clearly from siblings like get_app or seo_audit.

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 an explicit branch: 'If audit_ran is false, run seo_audit on production_url,' naming the sibling and the condition. It also warns 'do not poll repeatedly' since this is current state. The remaining gap is no explicit statement of when to prefer get_app or other status sources, but the guidance is otherwise concrete.

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.