Yuppsy

website_property_create

Creates Property website for the specified property id. See website_create for more details.

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": {
      "data": "<data>"
    },
    "name": "website_property_create"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	The property website data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedInput schema / properties / data / description
```
Added value: +"The property website data."
```

Changed3 schema fields changedNov 5, 2026

removedInput schema / properties / data / properties / type

Removed value: -{
-  "description": "Type of website: Agent, Property",
-  "enum": [
-    "None",
-    "Agent",
-    "Property"
-  ],
-  "type": "string"
-}

removedInput schema / properties / data / properties / typeId

Removed value: -{
-  "description": "The id of the data the website is based on: AgentId, PropertyId",
-  "type": "integer"
-}

addedInput schema / properties / data / required
```
Added value: +[
+  "propertyId"
+]
```

Changed6 schema fields changedNov 5, 2026

addedInput schema / properties / data / properties / domain / description

Added value: +"The domain of the website (e.g., example.com), if any. Not required."

addedInput schema / properties / data / properties / propertyId / description
```
Added value: +"Property id"
```

addedInput schema / properties / data / properties / subdomain / description

Added value: +"You can set a custom subdomain for the website (e.g., mycustomsubdomain.example.com). If UseTypeNameAsSubdomain is true, this property will be ignored."

addedInput schema / properties / data / properties / type / description
```
Added value: +"Type of website: Agent, Property"
```

addedInput schema / properties / data / properties / typeId / description

Added value: +"The id of the data the website is based on: AgentId, PropertyId"

addedInput schema / properties / data / properties / useTypeNameAsSubdomain / description

Added value: +"Set to true if the website should use the type name as a subdomain (e.g., agent.example.com, property.example.com). If false, the Subdomain property will be used instead."

AddedOct 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'Creates' but omits whether the site is published/live immediately, what happens on domain or subdomain conflicts, permission requirements, and whether the operation is reversible.

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?

The definition is only two sentences and front-loads the core action. The second sentence is a useful pointer, though it substitutes for rather than supplements behavioral detail.

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?

For a creation tool with a nested data object, no annotations, and no output schema, the description is thin. It should explain post-creation state, conflict behavior, and whether the website is live, rather than deferring entirely to website_create.

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 description coverage is 100%, and the nested fields (propertyId, domain, subdomain, useTypeNameAsSubdomain) are well documented in the schema itself. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('Creates') and resource ('Property website') scoped by 'the specified property id', which distinguishes it from website_agent_create and website_create. However, it defers substantive detail to the sibling tool rather than fully characterizing its own purpose.

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 explicit when-to-use or when-not-to-use guidance, only a pointer to 'website_create for more details'. The agent can infer this handles property websites, but nothing explains when to choose this over website_create, website_agent_create, or the subscription-based website tools.

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

All Yuppsy 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?