Skip to main content
Glama
Galbaz1

video-research-mcp

by Galbaz1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Video Continue Session

video_continue_session

Ask follow-up questions or give new instructions within an existing video analysis session by passing its session ID.

Instructions

Continue analysis within an existing video session.

Input Schema

NameRequiredDescriptionDefault
scopeNoExact workspace/notebook from creation; required for scoped sessions
promptYesFollow-up question or instruction
session_idYesSession ID from video_create_session

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / scope
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Exact workspace/notebook from creation; required for scoped sessions"
+}
  2. First observedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so safety is largely covered. The description adds the 'existing session' operational context but does not explain what 'continue' changes (state accumulation, cost, session lifetime).

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?

A single, front-loaded sentence with no wasted words. It is efficient, though arguably too terse to be maximally useful.

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?

An output schema exists so return values need not be explained, and annotations cover safety. Still, for a stateful session-continuation tool the description leaves unclear how the follow-up prompt interacts with prior context and whether continuation is expensive or bounded.

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 the schema already documents session_id, prompt, and scope. The description adds nothing beyond it, making the baseline 3 appropriate.

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?

States a clear verb+resource ('continue analysis' within a 'video session'), which distinguishes it from the sibling video_create_session. However, it does not name the sibling it complements or contrast with video_analyze, so differentiation relies on the name alone.

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 gives no explicit when-to-use, when-not-to-use, or alternative routing guidance. The requirement for an existing session is only inferable from the schema's session_id note, not the description itself.

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

Deploy Server

Other Tools