list_meeting_recapsList the key owner's personalized Referna intro, general, follow-up, and mixer recaps, newest first. Mixer recaps include the 1:1 checklist for each conversation the member joined.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of recaps, from 1 to 50. Default 20. | |
| offset | No | Number of newer recaps to skip. Default 0. |
| Name | Required | Description | Default |
|---|---|---|---|
| recaps | Yes | ||
| nextOffset | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "nextOffset": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "recaps": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "agendaCoverage": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "covered": {
+ "type": "boolean"
+ },
+ "note": {
+ "type": "string"
+ },
+ "topicKey": {
+ "type": "string"
+ },
+ "topicTitle": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "topicKey",
+ "topicTitle",
+ "covered",
+ "note"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "bodyText": {
+ "type": "string"
+ },
+ "conversations": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "agendaCoverage": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "covered": {
+ "type": "boolean"
+ },
+ "note": {
+ "type": "string"
+ },
+ "topicKey": {
+ "type": "string"
+ },
+ "topicTitle": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "topicKey",
+ "topicTitle",
+ "covered",
+ "note"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "partnerEmail": {
+ "type": "string"
+ },
+ "round": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "round",
+ "partnerEmail",
+ "agendaCoverage"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "counterpartEmail": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "kind": {
+ "type": "string"
+ },
+ "meetingDate": {
+ "type": "string"
+ },
+ "sessionId": {
+ "type": "string"
+ },
+ "subject": {
+ "type": "string"
+ },
+ "summaryCreatedAt": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "sessionId",
+ "kind",
+ "title",
+ "counterpartEmail",
+ "meetingDate",
+ "summaryCreatedAt",
+ "subject",
+ "bodyText",
+ "agendaCoverage",
+ "conversations"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "recaps",
+ "nextOffset"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful content context beyond that: it explains that mixer recaps include a 1:1 checklist and that ordering is newest first, though it omits pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, with the core purpose and ordering front-loaded, followed by a useful detail about mixer recap content. Zero obvious waste, though the second sentence could be trimmed if space were critical.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with rich annotations, 100% schema coverage, and an output schema, the description provides enough to call it correctly. Any remaining details, such as pagination defaults and response shape, are already covered by structured fields.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both limit and offset are fully documented in the schema. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('meeting recaps'), enumerates the recap types, and specifies ordering ('newest first'). It does not explicitly differentiate from the sibling get_meeting_recap, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The listing purpose is implied by 'List' and ordering, but there is no explicit guidance on when to use this tool versus get_meeting_recap. The reader can infer list-vs-get, but the description does not state the alternative or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.