Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

makeuseof_article

Retrieve MakeUseOf article content and metadata from a canonical URL for parsing, including title, authors, body paragraphs, and paywall status.

Instructions

Get MakeUseOf article content. Returns a MakeUseOf article by url, a canonical HTTPS article link. The response has the title, description, section, authors, lead image, publish and update times, the article body as paragraphs, and a paywalled flag. Section, author, tag, utility and video pages are not article URLs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical MakeUseOf article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 full disclosure burden, and it does well: it enumerates the returned payload (title, description, section, authors, lead image, publish/update times, body as paragraphs) and surfaces the important `paywalled` flag. It does not state what happens on a non-article or malformed URL, but the behavioral picture is richer than typical.

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 action, then the return shape, then the scope restriction. No filler or restatement of the tool name; every sentence earns its place.

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?

For a one-parameter fetch tool with no output schema and no annotations, the description supplies what is missing elsewhere: the full field list of the response, the paywall caveat, and the URL eligibility rule. Nothing an agent needs to call it correctly is absent.

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%, so the baseline is 3, but the description adds real meaning beyond the schema's terse 'Canonical MakeUseOf article URL' by stressing canonical HTTPS form and, more importantly, by defining which URLs are not articles. That extra constraint on the single parameter is genuinely useful.

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 and resource ('Get MakeUseOf article content') and immediately scopes it to a single article by URL. The closing sentence ('Section, author, tag, utility and video pages are not article URLs') actively distinguishes it from makeuseof_headlines, makeuseof_news and makeuseof_sections without the agent needing to open 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?

Gives clear when-not guidance by enumerating the page types that are not article URLs, which routes the agent away from this tool for listing-style requests. It stops short of naming the specific sibling to use instead (e.g. makeuseof_news), but the exclusion is concrete enough to prevent misuse.

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