Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_followup_analyze_transcript

Analyzes meeting transcripts to extract key moments, action items, signals, and performance data for structured follow-up.

Instructions

Extracts structured data from meeting transcripts: key moments, action items, signals, and performance analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enriched_eventYesThe enriched event data with transcript.{{enriched_event}}
user_roleNoUser's role for context-aware analysis. Falls back to followup_context if empty.{{followup_context.primary_role}}
user_goalsNoUser's goals for focused analysis. Falls back to followup_context if empty.{{followup_context.goals.raw_goals}}
followup_contextNoFull context from [F2] Load Followup Context. Used as fallback for role/goals.{{followup_context}}
modelNoModel for transcript analysis.gpt-5
output_variable_nameYesVariable name to store the analysis results.transcript_analysis
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. Only states extraction of structured data, no mention of side effects, authentication needs, or whether it modifies state.

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?

Single sentence is appropriately concise. Front-loaded with verb and purpose. Could mention output variable usage more explicitly but overall good.

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?

No output schema, but description covers high-level purpose. Lacks details on return format, error scenarios, or dependencies on followup_context from other tools.

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 coverage is 100%, so baseline is 3. Description adds no additional parameter-specific meaning beyond what schema already provides.

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?

Description clearly states the verb 'extracts', resource 'meeting transcripts', and specific outputs (key moments, action items, signals, performance analysis). Differentiates from sibling meeting tools by focusing on transcript analysis.

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?

No guidance on when to use this tool versus alternatives like meeting_followup_generate_all_artifacts or meeting_followup_load_followup_context. Lacks context about prerequisites or sequence.

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/OnStartups/agentai-mcp-server'

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