XenozMCP

by Xenoz-GitHub

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

cloud_publish_place

Publishes a Roblox place to a specified universe, supporting Play and Edit publish types.

Instructions

Publish a place to Roblox

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": {
      "universeId": "<universeId>",
      "placeId": "<placeId>"
    },
    "name": "cloud_publish_place"
  }
}

Input Schema

Name	Required	Description
`placeId`	Yes	Roblox Place ID to publish
`universeId`	Yes	Roblox Universe ID
`publishType`	No	Publish type (default Play)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 11, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose critical behavioral traits such as whether publishing is destructive (overwrites), what permissions are required, or any side effects. For a mutative action like publish, this is insufficient.

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

Conciseness3/5

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

The description is a single concise sentence, but it lacks structure and does not include important contextual information. It is not exemplary as it sacrifices completeness for brevity.

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?

Given the complexity of a publish action and the lack of annotations or output schema, the description is insufficiently complete. It omits details on return values, error handling, and prerequisites, leaving the agent underinformed.

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?

With 100% schema description coverage, the input schema already documents all parameters adequately. The description adds no additional meaning beyond the schema, meeting the baseline expectation.

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 the verb 'Publish' and resource 'a place to Roblox', making it specific and distinguishable from sibling tools like 'cloud_list_places' or 'open_place'. However, it lacks details on scope or output.

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 description provides no guidance on when to use this tool versus alternatives, no when-not conditions, and no prerequisites. This is a significant gap given the variety of sibling tools.

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