Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jerusalempost_news

Fetch recent Jerusalem Post front-page stories as structured JSON with title, URL, author, time, and image. Use it to monitor top headlines; premium items have no summaries.

Instructions

Get Jerusalem Post top stories. Returns recent Jerusalem Post front-page stories, with no parameters. Each item has its title, URL, author, publication time and image where available. Premium items keep their title and metadata but have no summary. Use jerusalempost-article to read an article and check its paywall flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.1/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 disclose return shape (title, URL, author, publication time, image) and the premium-item edge case (no summary). It omits pagination, rate limits, or maximum story count, but for a parameterless news feed this is substantial behavioral context.

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?

Front-loaded with purpose, then return details, edge case, and alternative. Slightly redundant phrases ('top stories' / 'front-page stories', 'with no parameters') keep it from a perfect score, but it is well organized and free of 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?

For a simple, parameterless feed with no output schema, the description covers purpose, return fields, the premium-summary exception, and the path to full article reading. Nothing essential for correct invocation is missing.

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?

The tool has zero parameters and the schema is empty, so the baseline is 4. The description's 'with no parameters' is redundant but does not harm clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Jerusalem Post top stories', 'recent Jerusalem Post front-page stories'). It distinguishes from the article-reading sibling, but does not clarify how it differs from jerusalempost_headlines or jerusalempost_sections.

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 explicit guidance to use `jerusalempost-article` for reading an article and checking its paywall flag. However, it does not mention when to prefer this tool over sibling listing tools like jerusalempost_headlines or jerusalempost_sections.

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