Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jerusalempost_article

Fetch Jerusalem Post article metadata and free body text from a canonical URL; paywalled articles are flagged, with paid paragraphs omitted.

Instructions

Get Jerusalem Post article content. Returns public Jerusalem Post article metadata and free body paragraphs. If isAccessibleForFree is false, paywalled is true and body paragraphs are omitted; paid article text is not represented by feed snippets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Jerusalem Post article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the paywall logic (isAccessibleForFree=false implies paywalled=true and omitted body paragraphs) and clarifies that paid text is not recoverable from feed snippets. This is meaningful behavioral context beyond a bare 'get article'. It does not cover auth or rate limits, keeping it short of a 5.

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 tight sentences, front-loaded with the core action and followed by the important paywall caveat. No filler or redundancy.

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 single-URL fetch tool with no output schema and no annotations, the description tells the agent what is returned (metadata + free body paragraphs) and what is not (paywalled text), which is nearly everything needed. Minor gap: no mention of error behavior for invalid/non-article URLs.

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%, so the single 'url' parameter is already documented as a 'Canonical Jerusalem Post article URL'. The description adds no syntax, format, or example beyond what the schema provides, so the baseline 3 applies.

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 Jerusalem Post article content') and clearly distinguishes itself from siblings like jerusalempost_headlines/news/sections, which list rather than fetch a single article. An agent can tell what it does without opening the 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 the required URL parameter and the sibling set (headlines/news/authors), but the description never explicitly says when to use this versus jerusalempost_headlines or jerusalempost_news, nor does it state prerequisites. It is adequate but leaves routing to inference.

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