Skip to main content
Glama

read_content

Extract text from a specific webpage section using heading name or CSS selector. Supports pagination to read large sections without refetching the full page.

Instructions

Extract plain text content from a specific page section identified by heading name or CSS selector. Supports pagination via offset and max_chars for large sections. Returns content, total character count, and whether more content is available. Use after page_map to read specific sections without re-fetching the entire page; use navigate instead when you need the full page content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
headingNoExact heading text to find (case-insensitive match). Extracts all content under that heading until the next heading of equal or higher level. If not found, the response lists available headings as a hint.
max_charsNoMaximum characters to return (default: 10000). Reduce for token efficiency; increase to get more content in one call.
offsetNoCharacter offset to start reading from (default: 0). Use with max_chars to paginate through large sections.
selectorNoCSS selector to extract content from (e.g. ".article-body", "#main-content"). Use when content isn't under a heading or you need a precise DOM target.
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses return fields (content, character count, more available), pagination behavior, and hints at heading-not-found behavior (lists available headings). Could add more detail on error handling but covers core behavior well.

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?

Two sentences, front-loaded with purpose, includes usage guidance at the end. No redundant or irrelevant content.

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 tool with 4 parameters, no annotations, no output schema, description covers usage context, behavior, return values, and alternatives. Slightly lacking in describing exact response format or error handling, but sufficient for basic use.

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 coverage is 100% with detailed parameter descriptions. The description reinforces usage patterns (pagination, alternative selector) but does not add significant new semantic information beyond the schema.

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 tool extracts plain text from a page section using heading name or CSS selector. It distinguishes from siblings page_map and navigate by specifying when to use each.

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?

Explicitly states when to use: after page_map to read specific sections without re-fetching, or use navigate for full page content. Also describes pagination support with max_chars and offset.

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/Mingye-Lu/AgenticCrawler'

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