Skip to main content
Glama

Yuppsy

website_property_publish

Publish a property website, making all the changes live on the website.

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": {
      "propertyId": "<propertyId>"
    },
    "name": "website_property_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyIdYesThe property id that the website belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / propertyId / description
      Added value: +"The property id that the website belongs to."
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare it as a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds real value by stating that ALL pending changes are pushed live, which is a meaningful blast-radius detail. It stops short of saying whether existing live content is overwritten, whether auth/permission is required, or what a failed publish leaves behind.

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?

One short sentence with the action front-loaded and no redundant wording. It is efficient, though its brevity borders on thinness for a live-site publishing action.

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?

For a one-parameter publishing action with annotations covering safety and full schema coverage, the description is adequate but minimal. It omits what state is required before publishing and what happens on success/failure, and with no output schema the agent gets no sense of the result.

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 coverage is 100% for the single propertyId parameter, so the schema already explains the input fully. The description adds no format, range, or validity detail beyond it, which is the expected baseline when the schema does the work.

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 names a specific verb+resource combination ('Publish a property website') and clarifies the effect ('all the changes live'), so the agent knows exactly what the operation does. It does not, however, distinguish this from near-identical siblings such as website_property_set_live, property_publish, or website_agent_publish.

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?

The phrase 'making all the changes live' hints that this follows editing, but there is no explicit when-to-use statement, no mention of prerequisites (e.g. draft changes existing), and no reference to the sibling tools that perform superficially similar publishes. Given how many publish/live siblings exist, this omission is costly.

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