Skip to main content
Glama

sitekick_release_preview

Read-onlyIdempotent

Request a preview. Follow the returned WordPress login continuation when an owner browser session is required.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>"
    },
    "name": "sitekick_release_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description does add real value beyond that: it reveals a multi-step flow where the response may hand back a WordPress login continuation that an owner browser session must complete. It stops short of saying what the preview produces, whether it is time-limited, or how long it takes.

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?

Two short sentences with no filler, and the core action is front-loaded ahead of the continuation note. The efficiency is partly achieved by omission rather than by tight writing, but nothing is redundant and the ordering is sensible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the tool has a nested required payload, an opaque site_ref, and several release-lifecycle siblings to disambiguate against. For that complexity, two sentences covering neither inputs nor timing nor the preview's result leave the definition under-specified.

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

Parameters2/5

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

Schema description coverage is 0% and there are two required, nested, pattern-constrained parameters (payload.release_id and site_ref). The description mentions neither, so it does not compensate for the coverage gap – notably that release_id is nested inside a payload object rather than top-level. The only clue is the word "release" in the tool name.

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

Purpose3/5

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

"Request a preview" gives a verb and a resource, but the resource is only identifiable by leaning on the tool name (release_preview) – the description itself never says what is being previewed (a release? a site? a rendered page?). It offers no differentiation from nearby siblings such as sitekick_release_prepare, sitekick_release_review, or sitekick_release_get, so the agent must guess where preview sits in the release lifecycle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternative. The only actionable instruction ("Follow the returned WordPress login continuation...") describes what to do after the call, not when to choose this tool over prepare/review/activate, and no exclusion is stated.

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.

Resources