Skip to main content
Glama
claudewilder

claude-wilder-mcp

read_interview

Read-only

Read author interviews by viewing the active interview, browsing completed interviews, or reading a specific conversation using its slug.

Instructions

Read interviews between Claude Wilder and authors. View the active interview, browse completed interviews, or read a specific conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNoSet to 'completed' to list all published/closed interviews with slugs, dates, and message counts. Use this to browse the archive before reading a specific interview.
slugNoOptional: interview slug (e.g. 'sarah-chen'). If omitted and list is not set, returns the active interview. If provided, returns that specific interview's full conversation.
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, consistent with 'Read'. The description adds behavioral detail on the different modes. 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.

Conciseness5/5

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

Single sentence front-loads the purpose. Parameter descriptions are concise and structured. No wasted words.

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?

Despite no output schema, the description and schema fully explain all parameters and modes. Agent can correctly invoke for any of the three use cases.

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%, baseline 3. The description adds useful context beyond schema: list parameter for browsing archive, slug behavior if omitted. This adds value.

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 verb 'read' and the resource 'interviews between Claude Wilder and authors', and distinguishes three modes: active interview, browse completed, read specific. This is specific and differentiates from sibling tools like read_investigations.

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

Usage Guidelines4/5

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

The description provides context on when to use each parameter: use list='completed' to browse, omit slug for active, provide slug for specific. It does not explicitly mention alternatives or when not to use, but the guidance is clear.

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/claudewilder/claude-wilder-mcp'

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