Skip to main content
Glama

summarize_text

Summarize long documents into key points using extractive and abstractive methods. Ideal for articles, reports, and transcripts.

Instructions

Summarize a long document or passage into key points.

Uses extractive and abstractive summarisation to distil the most important
information from the input. Suitable for news articles, reports, research
papers, meeting transcripts, and support tickets.

Args:
    text: Text to summarise. Works best with 200+ words of input.
          Handles articles, reports, and multi-paragraph passages.
    max_sentences: Target number of sentences in the output summary
                   (default 3, range 1–10). The model may produce fewer
                   if the source is already concise.

Returns:
    summary: The generated summary text.
    sentences: Number of sentences in the summary.
    compression_ratio: Input length divided by summary length.
    key_points: Bullet-point list of the main points (may be null
                for very short inputs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
max_sentencesNo
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It explains the approach (extractive and abstractive), constraints (input length, max_sentences range, potential fewer sentences), and return structure (summary, sentences, compression_ratio, key_points). 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?

Description is concise yet comprehensive, using clear sections for intro, use cases, parameters, and returns. No wasted sentences; every line adds information.

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 fully documents return values. Covers purpose, usage, parameters, and behavior. No gaps for an agent to invoke the tool correctly.

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 has 0% description coverage. Description adds full meaning: text parameter gets usage guidance and content type, max_sentences gets default, range, and behavior note. Also describes all return fields. Completely compensates for missing schema descriptions.

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 tool summarizes a long document into key points. It lists specific use cases (news articles, reports, etc.) and distinguishes from all sibling tools, which are unrelated (e.g., validate_email, dns_lookup).

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?

Provides suitable contexts (news, reports, transcripts) and input length recommendation (200+ words). Does not explicitly exclude contexts or mention alternatives, but sibling tools are all different so no ambiguity.

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/ForeverTools/kiprio-mcp'

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