Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Website: Show publish status

website_publish_status
Read-only

One site in detail: its public address, the cabinet editor link (editor_url), whether it is published, when it last changed and whether there are edits visitors do not see yet, its blocks (id, type, label, heading, visible, has_photos), its template, style, palettes and premium options, and the phone bar. Call it before editing a site to learn the block names. When the workspace's only site is an external one connected through «Сайт → Підключення» it answers status 'external_site' with connected_sites (no blocks — that site is edited on its own side). Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "website_publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteNoSite id, name or subdomain. Optional when the workspace has one site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The description confirms the read-only nature already declared in annotations and adds useful behavior beyond them, especially the external-site response with status 'external_site' and connected_sites but no blocks. It does not cover auth requirements or error behavior, but with annotations present that is a smaller gap.

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 dense but front-loaded, beginning with the resource and its returned fields before moving to usage and the external-site case. The final 'Read-only' sentence repeats the annotation and the field list is long, but there is little true filler.

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?

There is no output schema, so the description carries the burden of explaining return content, and it does so thoroughly with field names and the external-site exception. For a single-site read-only status tool with one optional parameter, this is complete enough to invoke correctly.

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?

The schema has 100% coverage for the single optional website parameter, already documenting id, name, or subdomain and the one-site default. The description does not add meaning beyond that schema text, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns one site in detail and enumerates the concrete fields exposed, such as address, editor_url, publish state, blocks, template, style, and phone bar. It does not explicitly differentiate itself from the sibling website_status, so it stops short of a 5.

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 a concrete usage rule: call it before editing a site to learn the block names. It also explains the external-site edge case, but it does not name alternatives or state when not to use this tool.

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

All OrgLines toolsInspect
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