Skip to main content
Glama

Zernote

by com.zernote
OverviewDiscussionsAdmin

Interviews Read

interviews_read
Read-only

Read interviews. Typical path: (1) action=list with summary_mode=brief (default) — returns the short # Summary. List items include need_approve_speakers (+ pending_speakers / hint): when true, show interviewer quote links then confirm via assign_speakers; one identity confirm backfills other interviews sharing voice_identity_id. Use summary_mode=brief for renaming or folder triage. Use summary_mode=full when Profile/Tools/Pains/Other topics are needed for deeper analysis. (2) call search when you need evidence or counter-evidence for a hypothesis; (3) use action=transcript with around_chunk_index from matching_chunks when a quote window is required. CITATION REQUIRED: when answering the user, actively cite evidence as markdown "verbatim quote" using interview_url / matching chunk url from tool results (includes ?t= when start_seconds is set). Prefer quotes over paraphrase.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoInterview UUID (required for get, status, transcript).
limitNoFor list: max interviews (default 20, max 100). For transcript: max characters (default 4000, max 20000).
actionYesRead action. Use list (brief or summary_mode=full) for overview; use transcript when you need a quote window.
offsetNoFor list: skip count. For transcript without around_chunk_index: character offset (default 0).
folder_idNoDeprecated alias for project_id.
inbox_onlyNoWhen true with action=list, list Inbox interviews (no project). Ignored if project_id is set.
notes_modeNoList only. none (default) = omit notes body. full = researcher notes (truncated on list). Use summary when notes are not required.
project_idNoOptional project UUID to filter list (alias: folder_id).
radius_charsNoTranscript only with around_chunk_index: chars before/after chunk match (default 1500, max 8000).
summary_modeNoList only. brief (default) = short # Summary for triage/rename. full = all summary_fragments (profile/tools/pains/other_topics) when brief is insufficient.
around_chunk_indexNoTranscript only: expand a window around this vector-search chunk_index (use instead of blind offset when available).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses default behavior (summary_mode=brief), list item fields like need_approve_speakers, the identity-backfill side effect, and the required citation format with URL construction. This is substantial behavioral context that annotations alone do not provide.

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 dense but logically ordered as a numbered workflow (list → search → transcript), with the citation requirement placed at the end as an actionable directive. Every sentence adds information, and the key workflow is front-loaded.

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 multi-action tool with no output schema, the description richly covers the common paths and return-ish details (summary fragments, need_approve_speakers, matching chunks). It omits guidance on action=get and action=status, which are listed in the schema and may need clarification, but the main paths are sufficiently complete.

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 coverage is 100%, so the baseline is 3; the description adds meaningful usage context for around_chunk_index ('from matching_chunks'), explains the interplay between summary_mode and triage vs. analysis, and clarifies that id is required for get/status/transcript. It does not deeply explain action=get or status, but parameters themselves are well covered.

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 opens with 'Read interviews' and immediately enumerates a concrete action list (list, get, status, transcript) with usage examples. It clearly differentiates this tool from the search sibling by explicitly directing evidence-seeking calls to `search` rather than this tool.

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?

It provides explicit when-to-use guidance: summary_mode=brief for renaming/folder triage, summary_mode=full for deeper analysis, `search` for evidence, and transcript with around_chunk_index for quote windows. This leaves no ambiguity about which sibling or action to choose.

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

All Zernote toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources