Sonar Connections

Publish an event website (organizers only)

site_publish

DestructiveIdempotent

Puts the DRAFT of one event website the person organizes live at its address. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId and what would go live (new, removed and changed sections, a new look, new pages), and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. The version live before it is kept, and site_undo_publish puts it back. site_edit does not publish. Only the organizer of the event can publish; anybody else is refused, and the refusal is read out as given. It requires a personal connector token. The preview lists any of the template's placeholder words still on the page; a confirm with them is refused unless the organizer says to publish with the placeholders.

Input Schema

Name	Required	Description
`siteId`	Yes	The site's id as site_list gives it.
`confirm`	No	True applies a previewed change; absent, the change is only previewed and nothing changes.
`changeId`	No	The id of a previewed change; required when confirm is true.
`eventIdOrName`	Yes	The event id or the event name as the organizer spells it.
`allowPlaceholders`	No	True publishes even though the draft still has the template's placeholder words; send it only when the organizer says to publish with the placeholders.

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`error`	No
`applied`	No
`changes`	No
`message`	No
`preview`	No
`changeId`	No
`liveLink`	No
`servedBy`	No
`versionsKept`	No
`draftPreviewLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / allowPlaceholders

Added value: +{
+  "description": "True publishes even though the draft still has the template's placeholder words; send it only when the organizer says to publish with the placeholders.",
+  "type": "boolean"
+}

AddedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already flag destructive=true, idempotent=true, and readOnly=false, but the description adds substantial context beyond them: the first call changes nothing, the prior live version is preserved, site_undo_publish restores it, a personal connector token is required, non-organizers are refused, and placeholder confirmations are refused unless explicitly allowed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition front-loads the core action and then walks through the preview/confirm workflow, permission rules, undo behavior, and placeholder exception. It is dense but every sentence contributes operational guidance for a destructive publishing tool.

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 a destructive, permission-gated publish operation with five parameters and an output schema, the description covers the full call sequence, failure conditions, authorization requirements, undo path, and placeholder handling. Return values need not be explained because an output schema exists.

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 meaningful procedural semantics: confirm absent means preview-only, confirm:true requires the preview's changeId, and allowPlaceholders is only for explicit placeholder approval. It stops short of documenting all parameter edge cases, but the workflow meaning is clear.

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 and resource: it publishes the DRAFT of one event website live at its address, restricted to organizers. It also distinguishes itself from site_edit (which does not publish) and site_undo_publish (which reverts), so an agent can tell it apart from siblings without opening schemas.

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?

Explicitly defines the required two-step workflow: first call without confirm to get a preview and changeId, read it back to the organizer, then call with confirm:true and that changeId only after approval. It also states when placeholders require allowPlaceholders and who is permitted to call it.

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

All Sonar Connections 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.

Resources

Need Help?