Skip to main content
Glama

Generate headlines for a text or topic in a chosen style

text_headlines
Read-only

Up to 10 headlines for a text or topic in one style: news, seo (under 60 characters, enforced in code), social or email subject. Each headline comes with its character count. Model output: check claims before publishing. Input text max 10,000 characters. Related tools on this server, for a different need: text_outline when you need to generate a structured outline for a topic or a text; text_chunk when you need to generate overlapping text chunks with character offsets. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "text_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoSource text (max 10,000 characters); use this or topic
countNoNumber of headlines, 1-10 (default 5)
styleNonews (default), seo, social or email
topicNoTopic (max 300 characters); use this or text

Output Schema

NameRequiredDescriptionDefault
styleNo
droppedNo
checkedAtNo
headlinesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / checkedAt
      Added value: +{}
    • addedOutput schema / properties / dropped
      Added value: +{}
    • addedOutput schema / properties / headlines
      Added value: +{}
    • addedOutput schema / properties / style
      Added value: +{}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond that: the seo 60-character limit is 'enforced in code', each headline returns its character count, output is model-generated so claims should be checked before publishing, input is capped at 10,000 characters, and pricing/failure-charging is spelled out. The x402 payment requirement is genuinely useful operational context. It stops short of describing the full return shape, but an output schema exists.

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?

Front-loaded with what it produces and the styles, then constraints, then alternatives, then price. Every sentence carries information, though the closing pricing/network sentence is long and slightly heavier than the rest of the definition.

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 generative tool with an output schema, the remaining burden is behavioral and operational, and the description covers style constraints, output content (character counts), trust caveat, input limits, and cost model. The dependency on x402 payment is noted, though it does not explain what an agent must do to satisfy it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both the text/topic duality, the 1-10 count range with default 5, and the style enumeration are already documented in the schema. The description reinforces the text-vs-topic choice and the count cap of 10 and the style list, which adds confirmation but no syntax or format detail beyond the schema. Baseline 3 applies.

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 states a specific verb and resource (generate up to 10 headlines) plus the exact style options: news, seo, social, email subject. It also names the two sibling tools (text_outline, text_chunk) with the different needs they serve, so an agent can distinguish it from nearby tools without opening any schema.

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?

Usage context is clear: 'for a text or topic in one style', with explicit routing to text_outline for structured outlines and text_chunk for overlapping chunks. It does not state when *not* to use it or how it compares to siblings like text_paraphrase, but the sibling guidance given is concrete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources