Skip to main content
Glama

sitekick_release_activate

DestructiveIdempotent

Activate exactly the browser-approved release using the returned publication_request. A tool confirmation cannot issue approval.

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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_release_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so safety basics are covered; the description then adds a genuine precondition the annotations cannot convey — that approval must originate from a real browser-approved flow, not from a mere tool confirmation. It still does not say what activation replaces (e.g., the current live release) or whether it is reversible, which is notable for a destructive, open-world operation.

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 wasted wording, and the core action is front-loaded. The second sentence's approval constraint is valuable, though the first sentence's dangling "publication_request" reference is a structural defect that costs clarity rather than length.

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

Completeness3/5

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

Because an output schema exists, return values need not be described, and the precondition on approval is covered. For a destructive, open-world mutation with a nested payload and 0% schema coverage, however, the definition should still state which prior tool produces the approval/operation identifiers and what state changes on success — neither is present.

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% across three required parameters, including a nested payload, so the description carries the full burden and largely fails it: approval_id, operation_id, site_ref, and idempotency_key are never explained. The only parameter-adjacent term, "publication_request," does not correspond to any schema property, adding confusion rather than meaning.

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?

"Activate exactly the browser-approved release" gives a specific verb and resource that clearly separates it from siblings like sitekick_release_prepare, _preview, _review, and _rollback. However, the phrase "using the returned publication_request" names a field that does not exist in the input schema (which requires payload.approval_id and payload.operation_id), which slightly muddies what input is actually expected.

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

Usage Guidelines3/5

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

The description implies this is the step that follows browser approval and warns that a tool confirmation cannot substitute for approval, which is useful intent guidance. It does not explicitly say when to prefer this over sitekick_release_prepare, _review, or _rollback, nor does it state prerequisites such as an existing approved review or what to do if approval is missing.

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