Skip to main content
Glama
kaiding-ucb

podcast-summarizer-mcp

by kaiding-ucb

analyze_video_result

Poll for the result of a video analysis job. Returns status and analysis when complete, or indicates pending, error, or not found.

Instructions

Poll for an analyze_video_start result. Blocks up to wait_seconds for a state change.

Default wait_seconds=10 keeps the blocking window well under the typical 60s MCP request timeout enforced by hosts. Smaller blocking window = guaranteed return well under 60s at the cost of more poll round-trips (cheap, ~1KB per poll).

Recommended pattern: call with wait_seconds=10 each poll. Cap total polling at ~90 iterations (~15 min) — most podcasts finish within 3-5 min. If a poll returns an MCP-transport error (not a status: "error" payload), the underlying job is likely still alive on the server — re-poll with the SAME job_id rather than starting over.

Args: job_id: The id returned by analyze_video_start wait_seconds: How many seconds to block waiting for completion (default 10, clamped to [0, 55] to stay safely under the MCP 60s request timeout)

Returns: { job_id, status, video_url, created_at, started_at, finished_at, result?, error?, attempts }

  • status="pending" or "running": still processing — poll again.

  • status="done": result holds the AnalysisResult dict (analysis, timestamps_valid, video_duration, vaneck_excluded, attempts, error=null).

  • status="error": error holds the message; result may hold a partial AnalysisResult.

  • status="not_found": job_id unknown (job purged after 6h TTL or wrong id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
wait_secondsNo
Behavior5/5

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

No annotations provided, but description fully discloses blocking behavior, clamping of wait_seconds to [0,55], all possible return statuses, and job TTL of 6 hours. No contradictions.

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?

Well-structured with paragraphs and bullet points, front-loaded core purpose. Slightly verbose due to recommended pattern details but every sentence adds value.

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

Completeness5/5

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

For a polling tool with 2 params and no output schema, description covers all needed context: return format, error handling, timeouts, polling limits, and job lifecycle. Very complete.

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

Parameters5/5

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

Schema coverage 0%, but description adds full meaning: job_id defined as id from analyze_video_start, wait_seconds explained with default and clamping range. Significantly adds beyond schema.

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?

Clearly states it polls for an analyze_video_start result. Distinguishes from siblings (analyze_video_start, analyze_videos_batch_result) by focusing on polling behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit recommended pattern: call with wait_seconds=10, cap polling at ~90 iterations, re-poll on transport errors. Rationale for default wait_seconds given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kaiding-ucb/podcast-summarizer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server