Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

iol_article

Extract structured IOL article data from canonical iol.co.za story URLs, returning title, authors, section, image, timestamps, and body paragraphs.

Instructions

Get IOL article content. Returns an IOL article by url, a canonical iol.co.za story link. The response has the title, description, section (the deepest in the breadcrumb, such as Crime and Courts), authors, lead image, publish and update times, and body paragraphs. Section, author, tag and search pages are rejected. paywalled is never set.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical IOL article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden and does so reasonably: it discloses the return shape (title, description, section, authors, lead image, times, paragraphs) and a genuine behavioral quirk ('paywalled is never set'). It omits auth/rate-limit context, but for a read-only article fetcher the disclosure is solid.

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?

Three tight sentences, front-loaded with the action, then the return fields, then the rejection constraints. No filler and every clause carries 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?

With no output schema and no annotations, the description covers the action, the valid input, the rejected inputs, and the response fields. An agent has everything needed to call it correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100% and the schema already names the parameter, so baseline is 3. The description adds value by specifying the URL must be a canonical story link and that non-article page URLs are rejected, which meaningfully constrains what is a valid value.

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?

States a specific verb+resource ('Get IOL article content') and immediately scopes it to a single canonical article URL. It is clearly distinguishable from the sibling iol_sections, iol_author, iol_headlines and iol_news 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?

Tells the agent the input must be a canonical 'iol.co.za' story link and explicitly rejects section, author, tag and search pages, which is strong when-not guidance. It stops short of naming the specific sibling tools to use for those rejected page types, so it is clear but not fully routing.

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