Yuppsy

property_insert_single_video

Add a single video to an existing property. This will NOT clear existing videos. If successful, it returns a success response along with the video id.

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": "property_insert_single_video"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	The property video item data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedInput schema / properties / data / description
```
Added value: +"The property video item data."
```
Changed3 schema fields changedNov 5, 2026
- addedInput schema / properties / data / properties / externalId / description
```
Added value: +"Property external id, if any."
```
- addedInput schema / properties / data / properties / mp4Uri / description
```
Added value: +"The external url of the mp4 video."
```
- addedInput schema / properties / data / properties / propertyId / description
```
Added value: +"The id of the property. Can be ignored if ExternalId is provided."
```
First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the operation is additive ('will NOT clear existing videos') and it returns a success response plus the video id. It says nothing about permissions, whether duplicate videos are rejected, or what happens on failure.

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?

Three short sentences, all front-loaded and functional: purpose first, the non-destructive guarantee second, the return shape last. Little waste, though 'it returns a success response along with the video id' is slightly verbose for what it conveys.

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

Completeness4/5

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

For a single-parameter nested-object tool with no annotations and no output schema, the description covers the essentials: scope, additive semantics, and the return value. The main residual gap is which identifier (propertyId vs externalId) is mandatory, which the schema itself leaves ambiguous.

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%, so each nested field (mp4Uri, externalId, propertyId) is already documented and a baseline of 3 applies. The description adds no meaning beyond the schema, notably omitting the 'externalId may substitute for propertyId' rule that the schema itself only states one-way.

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 gives a specific verb and resource ('Add a single video to an existing property'), and the word 'single' plus 'existing' implicitly separates it from the bulk sibling property_add_videos. It stops short of naming that sibling explicitly, so an agent must infer the distinction.

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?

Usage is only implied: 'existing property' signals the prerequisite that the property must already exist, and 'single' hints at the one-video-at-a-time case. There is no explicit statement of when to choose this over property_add_videos or property_add, and no exclusions are given.

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?