Skip to main content
Glama
AIMLPM

AIMLPM/markcrawl

search_pages

Search through previously crawled pages using one or more keywords. Results are ranked by matches and include URL, title, and text snippet. Requires a prior crawl to have populated the data.

Instructions

Search through previously crawled pages by keyword.

Performs case-insensitive keyword search across page titles and text content.
Results are ranked by the number of matching query words found. Each result
includes the page URL, title, and a text snippet showing context around the
first match.

This is a read-only operation on local files — no network requests are made.
Requires a prior crawl_site call to have populated the pages.jsonl file.

Args:
    query: Search query — one or more keywords separated by spaces. All words
        are searched independently (OR logic). Example: "authentication API key".
    jsonl_path: Full path to the pages.jsonl file from a previous crawl. If
        empty, defaults to <MARKCRAWL_OUTPUT_DIR>/pages.jsonl.
    max_results: Maximum number of results to return. Default: 10. Use lower
        values for focused searches, higher for comprehensive surveys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
jsonl_pathNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses it is read-only, operates on local files, uses OR logic, ranks by match count, and returns snippets. No side effects or auth requirements left unstated.

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?

Well-structured with summary then Args section. Slightly verbose but every sentence adds value. Front-loaded with purpose.

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?

Covers purpose, parameters, usage context, behavior, and output (URL, title, snippet). Output schema exists, so return details are sufficient. Complete for this tool.

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?

Despite 0% schema description coverage, description thoroughly explains each parameter: query as OR keywords with example, jsonl_path default path, max_results with usage guidance. Greatly adds meaning.

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 it searches crawled pages by keyword, specifies case-insensitive search across titles and text, and ranks results by matching words. It distinguishes from sibling tools like crawl_site, read_page, list_pages.

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?

Explicitly states it requires prior crawl_site call and is read-only with no network requests. However, does not explicitly compare to alternatives or state when not to use.

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/AIMLPM/markcrawl'

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