yzturkey-mcp

check_duplicate_idea

Check whether a video idea already exists in a channel's archive by comparing semantic embeddings. Returns matching past videos and flags duplicates above the similarity threshold.

Instructions

Check if a video idea or concept has already been produced in this channel.

Uses 768-dimensional semantic embeddings (cosine similarity) to compare your idea against the channel's entire past archive. Returns matching past videos and whether it exceeds the duplicate threshold (>0.78).

Args: channel_id: Channel UUID or slug. concept_text: The proposed headline or core concept to test for uniqueness.

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": {
      "channel_id": "<channel_id>",
      "concept_text": "<concept_text>"
    },
    "name": "check_duplicate_idea"
  }
}

Input Schema

Name	Required	Description	Default
`channel_id`	Yes
`concept_text`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining the 768-dimensional semantic embedding approach, cosine similarity, the >0.78 duplicate threshold, and what is returned. It does not explicitly state read-only behavior or failure modes, but the 'Check if' phrasing and algorithm details provide substantial transparency.

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

Conciseness5/5

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

The description is compact and front-loaded with the core purpose. It then adds valuable technical context and a clean Args section. No sentence is wasted, and the structure makes the tool's behavior immediately understandable.

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 two-parameter tool with an output schema present, the description is largely complete: it explains what the tool does, how it works, and what it returns. The main gap is the lack of explicit guidance on when to prefer this tool over the similar search_video_archive sibling, but the complexity is low enough that the provided details suffice for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does by providing concise meaning for both parameters: channel_id is a Channel UUID or slug, and concept_text is the proposed headline or core concept to test. This adds useful semantic information beyond the raw schema, though it could have included format or length expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: checking whether a video idea or concept has already been produced in a channel. It is specific about the verb, resource, and underlying comparison against the channel's past archive, distinguishing it from generic search or generation tools.

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?

The usage context is implied rather than explicit: it is for testing a concept's uniqueness before production, and the Arg description mentions 'to test for uniqueness.' However, it does not explicitly state when to use this tool over the similar sibling search_video_archive, nor provides any exclusions or alternative routing guidance.

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

Deploy Server