Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

news18_article

Retrieve News18 article content by canonical URL, including title, authors, lead image, timestamps, paywall status, and body paragraphs.

Instructions

Get News18 article content. Returns a News18 article by canonical url in the form /<section>/<slug>-<id>.html, optionally with a subsection. The response has title, description, authors, lead image, publication and update times, a paywalled flag and body paragraphs. section is the article's own category, so it can be a subsection such as business/markets that news18-sections does not list.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical News18 article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 it does useful work by disclosing the response shape (title, description, authors, lead image, publication/update times, a `paywalled` flag, and body `paragraphs`). It correctly implies a read-only fetch and warns about the paywalled flag, though it says nothing about auth, rate limits, or failure modes for a bad URL.

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 sentences, front-loaded with the core action, then the identifiable URL form, then the return shape and the section caveat. Every sentence earns its place with no filler.

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 a single required parameter, the description compensates by enumerating the returned fields and the paywall flag, and by clarifying the nested-section edge case. An agent has everything needed to call it 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% for the single `url` param, so baseline would be 3, but the description adds real meaning beyond the schema: the exact canonical path format and the note that `section` reflects the article's own category and may be a nested subsection. That is value the schema text alone does not convey.

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 (Get) and resource (News18 article content) and pins the scope with the canonical URL form `/<section>/<slug>-<id>.html`. An agent can distinguish this from siblings like news18_headlines, news18_news and news18_sections 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Get News18 article content' and the required URL shape, but there is no explicit when-to-use vs when-not-to-use guidance relative to the sibling news18_headlines/news18_news/news18_sections tools. The note that `section` may be a subsection news18-sections doesn't list is routing-adjacent but not selection guidance for this tool.

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