Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

summarize_conversation

Summarize a conversation by providing its conversation_id; the AI Action selects the most recent messages automatically, returning a summary with language support and optional date filters.

Instructions

Summarize a conversation by running an AI Action over its recent messages. USE WHEN: You want a conversation summarized and have a conversation_id. Message selection is handled for you — omit message_ids and the most recent messages are used. USE INSTEAD: run_ai_action if you already know exactly which message_ids to process, or want a non-summary AI Action. FIRST: prompt_id comes from list_ai_actions (field id) — call it first if you don't have one. FIRST: conversation_id comes from list_conversations (field results[].id) — call it first if you don't have one. EXAMPLE: {"conversation_id":"conv-abc","prompt_id":"prompt-abc","limit":50} RETURNS: Same as run_ai_action: {id, prompt_id, message_ids, responses: [{language, text?, markdown?, ...}], ...}. ERROR BAD_REQUEST: prompt_id is not a valid AI Action ID. — Call list_ai_actions to get valid prompt_id values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many recent messages to summarize when `message_ids` is omitted. Must be a positive integer; values above 50 are clamped to 50 (the upstream page limit). Ignored when `message_ids` is provided.
end_dateNoISO 8601 upper bound on message age; a UTC `Z` suffix or a numeric offset both work. Ignored when `message_ids` is given.
languageNoSummary language. Defaults to the original message language.
prompt_idYesAI Action ID, from `list_ai_actions` (its `id`).
start_dateNoISO 8601 lower bound on message age; a UTC `Z` suffix or a numeric offset both work. Ignored when `message_ids` is given.
message_idsNoSpecific messages to summarize. Omit to use the most recent messages, which is usually what you want — it saves a `list_messages` call.
conversation_idYesConversation to summarize, from `list_conversations`.
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.10.0
    • addedInput schema / properties / conversation_id / description
      Added value: +"Conversation to summarize, from `list_conversations`."
    • addedInput schema / properties / end_date / description
      Added value: +"ISO 8601 upper bound on message age; a UTC `Z` suffix or a numeric offset both work. Ignored when `message_ids` is given."
    • addedInput schema / properties / language / description
      Added value: +"Summary language. Defaults to the original message language."
    • addedInput schema / properties / limit / description
      Added value: +"How many recent messages to summarize when `message_ids` is omitted. Must be a positive integer; values above 50 are clamped to 50 (the upstream page limit). Ignored when `message_ids` is provided."
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / message_ids / description
      Added value: +"Specific messages to summarize. Omit to use the most recent messages, which is usually what you want — it saves a `list_messages` call."
    • addedInput schema / properties / prompt_id / description
      Added value: +"AI Action ID, from `list_ai_actions` (its `id`)."
    • addedInput schema / properties / response_fields
      Added value: +{
+  "description": "Dot-path allowlist to shrink the response, e.g. [\"results.id\",\"total\"]. Omit for the full payload.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / start_date / description
      Added value: +"ISO 8601 lower bound on message age; a UTC `Z` suffix or a numeric offset both work. Ignored when `message_ids` is given."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations are minimal (readOnlyHint=false, no destructiveHint), so the description carries the burden. It discloses that message selection is automatic, states the return format mirrors `run_ai_action`, and documents the BAD_REQUEST error case. It does not discuss side effects like resource consumption or rate limits, but it adds meaningful behavioral context beyond the annotations.

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?

Structured with clear headers (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, ERROR) that front-load the most critical information. Each section earns its place, though the text is somewhat lengthy. The structure compensates for verbosity, making it easy to scan.

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?

Given 8 parameters, no output schema, and moderate complexity, the description covers all essential context: prerequisites, usage conditions, an example, the exact return shape, and an error condition. An agent has everything needed to invoke the tool correctly without additional lookups.

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 covers all parameters, but the description adds significant usage guidance: it explains the `message_ids` omission behavior (uses recent messages, saves a `list_messages` call), tells the agent to get `prompt_id` from `list_ai_actions` and `conversation_id` from `list_conversations`, and provides an example. This clearly exceeds the baseline.

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 a precise statement of what the tool does: 'Summarize a conversation by running an AI Action over its recent messages.' It clearly names the resource (conversation) and mechanism (AI Action), and explicitly differentiates from the sibling `run_ai_action` by stating when to use one over the other. No ambiguity.

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 USE WHEN and USE INSTEAD directives, naming `run_ai_action` as the alternative and the condition that selects it (knowing exact message_ids or wanting a non-summary action). Also includes FIRST prerequisites for obtaining `prompt_id` and `conversation_id` from sibling tools, leaving nothing to inference.

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

Deploy Server

Other Tools