Skip to main content
Glama

Yuppsy

property_set_videos

Destructive

Set videos for an existing property. This will clear all existing videos and add the new ones. If successful, it returns the IDs of the newly added videos. data => { id = 'video id', uri = 'video uri' }

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_set_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe property video data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, but the description earns credit by spelling out exactly what is destroyed ("This will clear all existing videos and add the new ones") and by stating the return value (IDs of newly added videos), which no output schema provides. The only gap is that it says nothing about permissions or partial-failure behavior.

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 first three sentences are front-loaded and waste no words. The final data-shape line is both extraneous (the schema covers it) and incorrect, so it detracts rather than adds.

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 single-parameter destructive mutation, the definition covers the essential facts: prerequisite, destructive replace semantics, and return value. It is undermined by the inaccurate payload example, which is the one thing an agent would need to get right.

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 coverage is 100%, so the schema already fully documents data.mp4Uri and data.propertyId. The description's trailing line "data => { id = 'video id', uri = 'video uri' }" describes a different shape than the schema requires and would actively mislead an agent constructing the payload.

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 uses a specific verb and resource ("Set videos for an existing property") and clarifies the operation is a full replacement rather than an append. It does not name or distinguish itself from siblings like property_insert_single_video or property_delete_video, so the agent must infer that this is the bulk-replace variant.

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?

"For an existing property" implies a prerequisite (the property must already exist) and the destructive replace semantics imply when to prefer this over an incremental insert. However, there is no explicit when-to-use/when-not-to-use statement or pointer to an alternative tool for adding a single video.

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